LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-22-2016, 04:38 PM   #1
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 15.0 + Multilib
Posts: 2,159

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Current - e2fsprogs Fri May 20 21:20:29 UTC 2016 and 64-bit fsck


All --

The two threads about the new 64-bit defaults in /etc/mke2fs.conf worry me a bit.

http://www.linuxquestions.org/questi...ng-4175580324/
and
http://www.linuxquestions.org/questi...ed-4175580346/

Specifically, is it safe to run fsck on the existing 32-bit ext4 partitions on my system ?

I did not have any problems after the Friday May 20 Updates to Current but on the other hand, I've not run fsck since that update either.

Would it be wise to revert /etc/mke2fs.conf to the 32-bit default from before the update to Current before fsck is run ( i.e. before my next reboot, just in case fsck happens to run ) ?

tune2fs seems OK with the new /etc/e2fsck.conf file ( below ) and I've got no /etc/e2fsck.conf file, but does /etc/mke2fs.conf affect fsck ?

Thanks.

-- kjh

Code:
# tune2fs -l /dev/sda3

tune2fs 1.43 (17-May-2016)
Filesystem volume name:   <none>
Last mounted on:          /
Filesystem UUID:          e1781832-5e18-46a6-832f-17b7ca96c075
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              55705600
Block count:              222822400
Reserved block count:     11141120
Free blocks:              157365123
Free inodes:              54336719
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      970
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Mon Feb  8 07:07:04 2016
Last mount time:          Sat May 21 05:51:35 2016
Last write time:          Tue May 17 19:58:38 2016
Mount count:              80
Maximum mount count:      -1
Last checked:             Mon Feb  8 07:07:04 2016
Check interval:           0 (<none>)
Lifetime writes:          4892 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
First orphan inode:       26477084
Default directory hash:   half_md4
Directory Hash Seed:      63e8c128-9163-467f-98db-94f233092518
Journal backup:           inode blocks
Code:
# diff -Naur /etc/mke2fs.conf-old-B60520 /etc/mke2fs.conf

--- /etc/mke2fs.conf-old-B60520 2015-11-10 15:07:05.000000000 -0600
+++ /etc/mke2fs.conf            2016-05-20 11:56:57.000000000 -0500
@@ -11,12 +11,11 @@
                features = has_journal
        }
        ext4 = {
-               features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
-               auto_64-bit_support = 1
+               features = has_journal,extent,huge_file,flex_bg,64bit,dir_nlink,extra_isize
                inode_size = 256
        }
        ext4dev = {
-               features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
+               features = has_journal,extent,huge_file,flex_bg,inline_data,64bit,dir_nlink,extra_isize
                inode_size = 256
                options = test_fs=1
        }
 
Old 05-22-2016, 04:54 PM   #2
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
Well I have both 32 and 64 bit systems and do not seem to have a problem when booting into my 32 bit and it runs fsck on the 64 bit operating system hard drive.
or problems the other way around. But that is interesting mmmm.

Last edited by Drakeo; 05-22-2016 at 04:55 PM.
 
1 members found this post helpful.
Old 05-22-2016, 05:26 PM   #3
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
As far as I know, the issue is only on filesystem creation (mkfs), not running checks on the system (fsck). So, running checking the drive shouldn't prevent any problems.
 
1 members found this post helpful.
Old 05-22-2016, 06:45 PM   #4
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 15.0 + Multilib
Posts: 2,159

Original Poster
Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Thanks Y'All !

And having Alien Bob's ( Eric's ) liveslak on a USB Thumb Drive is a comforting thought as well

-- kjh
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] tar-1.29 (current -- Fri May 20 2016) : --exclude-from=FILE Thom1b Slackware 4 05-22-2016 02:51 AM
Update Current Sun Jan 17 07:24:08 UTC 2016 burdi01 Slackware 1 01-17-2016 11:14 PM
[SOLVED] /dev/net missing in Current's Fri Nov 20 21:52:15 UTC 2015 update tux_dude Slackware 15 11-22-2015 10:57 PM
Issues in -current as at Fri Aug 21 21:17:48 UTC 2015 allend Slackware 29 08-26-2015 09:49 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:42 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration