Le Mon, 14 Apr 2008 00:22:28 +0200
Petter Reinholdtsen <[EMAIL PROTECTED]> a écrit:
> > Because sdb1 is a big partition and the fsck take a long time so
> > it's interesting to have a progress bar, otherwise you can think
> > that there's a problem because you've seen a progress bar for the
> > ot
> Because sdb1 is a big partition and the fsck take a long time so
> it's interesting to have a progress bar, otherwise you can think
> that there's a problem because you've seen a progress bar for the
> others partitions.
Right. Is this the same issue as bug #432865?
Happy hacking,
--
Petter R
> I think that the master script of the action is
> /etc/init.d/checkfs.sh
I believe so too. :)
> As you can see there is -C0 option for all the sdax but not for
> sdb1.
OK. And why is this a problem? Why did you expect -C0 to be used for
sdb1?
> But I don't know all the processus so perhaps
Le Sun, 13 Apr 2008 18:04:58 +0200
Petter Reinholdtsen <[EMAIL PROTECTED]> a écrit:
> > On my system I've two hd (sda and sdb), when checkfs.sh runs on the
> > first one there is the -C0 option which is applied but not on the
> > second one.
>
> I did not understand this request. Can you elabora
> On my system I've two hd (sda and sdb), when checkfs.sh runs on the
> first one there is the -C0 option which is applied but not on the
> second one.
I did not understand this request. Can you elaborate a bit more?
Given the script name, I assume this is related to the way fsck is
called. Why
Package: initscripts
Version: 2.86.ds1-55
Severity: normal
On my system I've two hd (sda and sdb), when checkfs.sh runs on the
first one there is the -C0 option which is applied but not on the second
one.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, '
6 matches
Mail list logo
