search for: fs_passno

That seems to be the indication given by this webpage http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html However, default install of Redhat 7.2 setsup fs_passno(6th field of /etc/fstab) as 2 which asks you if you want to run fsck after an unclean shutdown The question is, is fsck required after an unclean shutdown or should one just rely on journal replay. What does fsck do when it sees an unclean ext3 filesystem Regards, Yusuf -- Yusuf Goolamabbas yus...

...: UUID=d5ff30df-9e1d-4fc8-99b6-845ffa6509db / xfs defaults 0 0 UUID=052f75bc-0513-45e0-a01f-06c9a698469f /mnt/data xfs defaults 0 0 UUID=732dafbd-2f14-4dd6-8513-1504b13302f1 swap swap defaults 0 0 Fields fs_freq and fs_passno are all set to 0. This fstab was generated by the installer and not yet modified. To reproduce this, I've installed a minimal centos on a VM and the same problem persists. I don't know if this is a bug or if there is a new system that does not require the last two field on C7 REL 1503....

From: Mark Milhollan Sent: April 21, 2015 05:35 > On Mon, 20 Apr 2015, Hugh E Cruickshank wrote: > > >CentOS 6 > > >From ''man fstab'' ... > > The sixth field, (fs_passno), is used by the fsck(8) > program to determine the order > in which filesystem checks are done at reboot time. > The root filesystem should be > specified with a fs_passno of 1, and other > filesystems should have a fs_passno of > 2. Filesystems withi...

...xfs >> defaults 0 0 >> UUID=052f75bc-0513-45e0-a01f-06c9a698469f /mnt/data xfs >> defaults 0 0 >> UUID=732dafbd-2f14-4dd6-8513-1504b13302f1 swap swap >> defaults 0 0 >> >> >> Fields fs_freq and fs_passno are all set to 0. This fstab was generated >> by the installer and not yet modified. >> >> To reproduce this, I've installed a minimal centos on a VM and the same >> problem persists. >> >> I don't know if this is a bug or if there is a new system that do...

...lled filesystem, and it was shut down uncleanly, just replay the journal and check for immediately obvious problems, but don't bother scanning the whole filesystem unless there's a '-f' in sight". AFAICT, the usual way of handling ext3 filesystems seems to be to mark them with fs_passno=0, so they never get fscked from the init scripts - but the journal gets replayed, and a few things get checked at mount time. If mount fails - because something horrible really did happen - then the /etc/rc.sysinit doesn't seem to have any way of coping, or dropping to an interactive shell....

On 06/08/2015 06:29 PM, Peter wrote: > On 06/09/2015 12:19 PM, John R Pierce wrote: >> On 6/8/2015 5:08 PM, g wrote: >>> ie, partition for boot, partition for swap, partition for /, partition >>> home, partition for usr, partition for var, partition for home2, >>> partition for what ever. >> >> >> that model is not generally recommended

...ffa6509db / xfs > defaults 0 0 > UUID=052f75bc-0513-45e0-a01f-06c9a698469f /mnt/data xfs > defaults 0 0 > UUID=732dafbd-2f14-4dd6-8513-1504b13302f1 swap swap > defaults 0 0 > > > Fields fs_freq and fs_passno are all set to 0. This fstab was generated > by the installer and not yet modified. > > To reproduce this, I've installed a minimal centos on a VM and the same > problem persists. > > I don't know if this is a bug or if there is a new system that does not > require the...

...0 0 >>> UUID=052f75bc-0513-45e0-a01f-06c9a698469f /mnt/data xfs >>> defaults 0 0 >>> UUID=732dafbd-2f14-4dd6-8513-1504b13302f1 swap swap >>> defaults 0 0 >>> >>> >>> Fields fs_freq and fs_passno are all set to 0. This fstab was generated >>> by the installer and not yet modified. >>> >>> To reproduce this, I've installed a minimal centos on a VM and the same >>> problem persists. >>> >>> I don't know if this is a bug or if there...

...t. Might there be an interaction occuring between RAID1 and Ext3 perhaps? Raid was setup using the RedHat Installation CD option 'Make Raid'. Might the errors not be 'real' - with fsck not understanding Ext3 journalling sufficiently. If this is the case, should the last parameter (fs_passno) in /etc/fstab be '0', preventing filesystem checks. Might there be a bug in ext3? Might Ext-3 not cope with power resets in the same way as I imagined? Thanks in advance for any comments. /Mark __________________________________________________ Do You Yahoo!? Everything you'll ever...

hello everyone. i guess this has been asked before, but haven't found it in the faq. i have the following issue... it is not uncommon nowadays to have desktops with filesystems in the order of 500gb/1tb. now, my kubuntu (but other distros do the same) forces a fsck on ext3 every so often, no matter what. in the past it wasn't a big issue. but with sizes increasing so much, users are