* [linux-lvm] serializing fsck
@ 2000-12-16 21:18 zoo1
2000-12-17 14:56 ` Harri Haataja
0 siblings, 1 reply; 2+ messages in thread
From: zoo1 @ 2000-12-16 21:18 UTC (permalink / raw)
To: linux-lvm
(is Ted Ts'o reading this list, by any chance?)
it seems my fsck on bootup is having trouble figuring out on which
physical devices various lvols reside, and so is starting up all the
fsck's simultaneously. i'm working around this by fiddling with the fsck
parameters in /etc/fstab, and i suspect that's probably the only really
general solution (since striping would throw wrenches into the works
anyway), but i'd like to know if i've overlooked some other possibility?
--
PGP/GnuPG key (ID 1024D/BFE0D6D0) available from keyservers everywhere
"Everything I am today, I owe to people whom it is now too late
to punish."
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [linux-lvm] serializing fsck
2000-12-16 21:18 [linux-lvm] serializing fsck zoo1
@ 2000-12-17 14:56 ` Harri Haataja
0 siblings, 0 replies; 2+ messages in thread
From: Harri Haataja @ 2000-12-17 14:56 UTC (permalink / raw)
To: linux-lvm
On Sat, 16 Dec 2000 zoo1@corecomm.net wrote:
> it seems my fsck on bootup is having trouble figuring out on which
> physical devices various lvols reside, and so is starting up all the
> fsck's simultaneously. i'm working around this by fiddling with the fsck
> parameters in /etc/fstab, and i suspect that's probably the only really
> general solution (since striping would throw wrenches into the works
> anyway), but i'd like to know if i've overlooked some other possibility?
E2fsck seems to do that on any disk on me. I've ended up adjusting the
order in fstab by hand.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-12-17 14:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-12-16 21:18 [linux-lvm] serializing fsck zoo1
2000-12-17 14:56 ` Harri Haataja
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox