From: zoo1@corecomm.net
To: linux-lvm@sistina.com
Subject: [linux-lvm] serializing fsck
Date: Sat, 16 Dec 2000 16:18:10 -0500 [thread overview]
Message-ID: <20001216161810.A1006@bar.nowhere> (raw)
(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."
next reply other threads:[~2000-12-16 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 21:18 zoo1 [this message]
2000-12-17 14:56 ` [linux-lvm] serializing fsck Harri Haataja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001216161810.A1006@bar.nowhere \
--to=zoo1@corecomm.net \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox