fsck.ext3 different?

[Rajmund Krivec]

Is it possible that FC2 fsck.ext3 wrill not be able to verify
the FC4 partitions, and therefore it will not be able to mount
FC4 partitions into FC2? (Multiboot, cross mounting of user
areas while transitioning).

FC2 could not boot smoothly while a FC4T2 partition was in
/etc/fstab.

Rajmund

[Arjan van de Ven]

On Wed, 2005-04-20 at 10:06 +0200, Rajmund Krivec wrote:
>  Is it possible that FC2 fsck.ext3 wrill not be able to verify
>  the FC4 partitions, and therefore it will not be able to mount
>  FC4 partitions into FC2? (Multiboot, cross mounting of user
>  areas while transitioning). 
yes fc2 fcsk will not understand some things that fc4 ext3 uses, like
online resizing preparations etc. the kernel ought to, but to actually
fsck a volume the requirements of understanding all bits are higher than
just being allowed to ignore a few things you don't understand....

[Mary Ellen Foster]

On 4/20/05, Rajmund Krivec <Rajmund.Krivec(a)ijs.si&gt; wrote:
>  Is it possible that FC2 fsck.ext3 wrill not be able to verify
>  the FC4 partitions, and therefore it will not be able to mount
>  FC4 partitions into FC2? (Multiboot, cross mounting of user
>  areas while transitioning).
>  
>  FC2 could not boot smoothly while a FC4T2 partition was in
>  /etc/fstab. 
You can mount partitions without running fsck, though -- just put a
"0" in the last field in /etc/fstab and it'll mount without checking.
This has worked in my experience, but I don't claim to understand all
of the issues and maybe this is just papering over some looming
problem ... but as long as you boot FC4 occasionally, the partition
will still get checked, right?

MEF

-- 
__ Mary Ellen Foster __ http://homepages.inf.ed.ac.uk/mef/ __
"One of the main causes of the fall of the Roman Empire was that, 
lacking zero, they had no way to indicate successful termination 
of their C programs." (Robert Firth)

[Stephen C. Tweedie]

Hi,

On Wed, 2005-04-20 at 09:59, Mary Ellen Foster wrote:

>  You can mount partitions without running fsck, though -- just put a
>  "0" in the last field in /etc/fstab and it'll mount without checking.
>  This has worked in my experience, but I don't claim to understand all
>  of the issues and maybe this is just papering over some looming
>  problem ... but as long as you boot FC4 occasionally, the partition
>  will still get checked, right? 
Not really.

With a journaling filesystem, "fsck" actually performs two completely
separate functions.  One is the normal recovery that occurs to make the
filesystem consistent after an uncontrolled reboot; the other is a full
consistency check which scans the entire filesystem and corrects any
problems seen.

The recovery bit is very quick, which is why reboots are faster with
journaling filesystems.  And the kernel can do a recovery itself, so if
you don't fsck the filesystem at boot time, it doesn't matter.

But when a full consistency check is required --- either because the
"time until next check" counters have expired (see man tune2fs), or
because the kernel previously encountered a problem on the filesystem
and marked it as containing an error, then you need to have a fsck that
understands all of the current features on that filesystem.

So if you periodically boot to FC4 from an FC2 machine, all that happens
is that if there's no error, nothing gets checked (ie. no improvement);
and if there _is_ an error, then most of your boots are still into FC2,
so at that point the machine won't boot.

You can either keep a newer rescue disk around to do the forced fsck if
you ever get errors on the fs, or simply disable the features you don't
want (with tune2fs), and do a forced fsck to clean up.

--Stephen