Hi,
I think you've included enough info. I don't know if fsck is supposed
to work that way with journalling but if not, it'd be nice to get that
documented.
I'd also like to see that "timestamp mismatch" print out the
timestamps so we can see what's going on. Eg, if your clock is somehow
skewing.
Adrian Chadd freebsd.org> writes:
>
> Please file a PR and put as much debugging output as you can.
> ...
Because this is a case of clean shutdown and oing on purpose to single user
mode to see how these hings behave, I assume I can go and try again and collect
similar info.
But, is there any d
Please file a PR and put as much debugging output as you can.
I haven't had it fail for me on any of my test machines that panic
_very frequently_. But I only hvae a single disk with minimal IO, I
haven't had it crash doing lots of ongoing server style iO.
adrian
On 11 March 2012 00:19, Alex K
On 10.03.2012 14:01, jb wrote:
Hi,
FB9.0-RELEASE; no updates or recompilation.
In multi-user mode:
$ mount
/dev/ada0s2a on / (ufs, local, journaled soft-updates)
The fs was in normal state (no known problem, clean shutdown),
Booted by choice in single-user mode.
# mount
/dev/ada0s2a on / (ufs
Hi,
FB9.0-RELEASE; no updates or recompilation.
In multi-user mode:
$ mount
/dev/ada0s2a on / (ufs, local, journaled soft-updates)
The fs was in normal state (no known problem, clean shutdown),
Booted by choice in single-user mode.
# mount
/dev/ada0s2a on / (ufs, local, read-only)
# fsck -F
