:But as it comes out I had (in fact :( ) a typo in the disklabel.
:
:I checked the disklabel two times before my post to -current, but
:I had obviously a little problem with my 'eye-brain-interlink'.
:
:I really shouldn't admit this in this forum, should I? ... But
:in relabeling the disk I left
Hi,
... thanks for your assistance.
I
On Fri, Jan 28, 2000 at 08:22:32AM -0800, Rodney W. Grimes wrote:
> Next step is run the ``save'' fsck:
> fsck -n /scratch >/someplacewithspace 2>&1
> > there is some illuminated filesystem-hacker who would like to
> > take a peek. (I would allow ssh-acce
:Hi there,
:
: I reported a former heavy filesystem crash recently; have a look
: at:
:
:http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/2123.freebsd-current
:
: I got it again.
: Meanwhile my system got updated to
: FreeBSD abc.xyz.de 4
...
>
> Starting an 'fsck' results in:
>
> cage:[/] # fsck /scratch
> ** /dev/da1s1g
> ** Last Mounted on /scratch
> ** Phase 1 - Check Blocks and Sizes
> PARTIALLY TRUNCATED INODE I=16
> SALVAGE? [yn] ^C
> * FILE SYSTEM MARKED DIRTY *
Next step is run the `
Hi there,
I reported a former heavy filesystem crash recently; have a look
at:
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/2123.freebsd-current
I got it again.
Meanwhile my system got updated to
FreeBSD abc.xyz.de 4.0-CURRENT
