Re: another hint for fsck for large filesystems
--- On Wed, 1/6/10, Alexander Hall alexan...@beard.se wrote:
You should be able to get the same result
using proper values for fs_passno in /etc/fstab.
One would hope so, but I don't think that's the case.
First, the man page says
the root filesystem should be specified with
a fs_passno of 1, and other filesystems
should have a fs_passno of 2. Filesystems
within a drive will be checked sequentially,
but filesystems on different drives will be
checked at the same time to utilize
parallelism available in the hardware.
Second, in fsck/preen.c I see a construct like this
for (passno = 1; passno = 2; passno++) {
...
... if (passno == 2 fs-fs_passno 1) {
For some reason, many years ago, fsck was optimized to run in parallel for
efficiency. It's unfortunate that the fstab file can't be used to provide
better control over the parallelism.
Re: another hint for fsck for large filesystems
Bohdan Tashchuk wrote:
--- On Wed, 1/6/10, Alexander Hall alexan...@beard.se wrote:
You should be able to get the same result using proper values for
fs_passno in /etc/fstab.
One would hope so, but I don't think that's the case.
First, the man page says
the root filesystem should be specified with a fs_passno of 1, and
other filesystems should have a fs_passno of 2. Filesystems within a
drive will be checked sequentially, but filesystems on different
drives will be checked at the same time to utilize parallelism
available in the hardware.
Second, in fsck/preen.c I see a construct like this
for (passno = 1; passno = 2; passno++) { ... ... if (passno == 2
fs-fs_passno 1) {
Oh yes it seems you're right, and it goes a long way back too. I wonder
if it ever worked the way I've always interpreted the man page...
For some reason, many years ago, fsck was optimized to run in
parallel for efficiency. It's unfortunate that the fstab file can't
be used to provide better control over the parallelism.
Re: another hint for fsck for large filesystems
Bohdan Tashchuk wrote: Sorry I'm not subscribed to the misc@ list, I read on a web archive. So I can't reply directly to the recent discussion about how to do newfs / fsck etc on large file systems (memory issue). I have one box with relatively limited memory and had to make a change directly to /etc/rc (yes, horrors)!. The change is fsck -p -l 1 This keeps fsck from checking more than one disk in parallel. You should be able to get the same result using proper values for fs_passno in /etc/fstab. $ man fstab /passno /Alexander
another hint for fsck for large filesystems
Sorry I'm not subscribed to the misc@ list, I read on a web archive. So I can't reply directly to the recent discussion about how to do newfs / fsck etc on large file systems (memory issue). I have one box with relatively limited memory and had to make a change directly to /etc/rc (yes, horrors)!. The change is fsck -p -l 1 This keeps fsck from checking more than one disk in parallel.
