Doug Barton wrote:
> I brought the fsck_y_enable stuff in, I'll try to take a look at it this
> week.
Just to avoid misunderstandings: That all worked fine a few weeks ago...
that was the second to last time I needed it (because I accidentally
pulled the wrong plug).
Regards,
--
Michael Nott
I brought the fsck_y_enable stuff in, I'll try to take a look at it this
week.
Doug
On Mon, 8 Jul 2002, Michael Nottebrock wrote:
> Georg-W. Koltermann wrote:
> > Yes, I see that as well. Another symptom is that fsck -p now always
> > announces "unexpected inconsistencies" and drops back to si
Similar things happen to me... Also when I do an 'fsck -y' fsck will
fsck each partition until it hits one with problems. It fixes the
problems, then exits (does not continue to the next partition). I
wind up having to run fsck five or six times to get it to fsck all
the part
Georg-W. Koltermann wrote:
> Yes, I see that as well. Another symptom is that fsck -p now always
> announces "unexpected inconsistencies" and drops back to singleuser when
> it indeed was able to fix the problems, i.e. it marks the filesystem
> clean and a manual fsck does not report anything unus
On Sun, Jul 07, 2002 at 09:41:14PM -0700, Peter Wemm wrote:
> It seems to be aborting the 'process all file systems' loop when it modifies
> a file system. eg:
<...>
> [[[ Uhh, what? What about the rest of the file systems? ]]]
I saw this once yesterday night, (after getting an "automagic reb
Yes, I see that as well. Another symptom is that fsck -p now always
announces "unexpected inconsistencies" and drops back to singleuser when
it indeed was able to fix the problems, i.e. it marks the filesystem
clean and a manual fsck does not report anything unusual.
My last cvsup was with date=2
