dump/mksnap_ffs & fsck failure
Kris Kennaway
kris at obsecurity.org
Thu Oct 7 06:32:40 PDT 2004
On Thu, Oct 07, 2004 at 12:08:03PM +0100, Chris Elsworth wrote:
> Hello all,
>
> Is this likely to be filesystem corruption in a really bad way, or a
> ufs bug:
>
> # /sbin/dump -0 -LuaC32 -f /backup/root.dump /
> mksnap_ffs: Cannot create //.snap/dump_snapshot: Input/output error
>
> # fsck_ufs /dev/mirror/gma
> ** /dev/mirror/gma (NO WRITE)
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> fsck_ufs: cannot alloc 4294967292 bytes for inoinfo
Why can't it write to the device? Is it mounted read-write? Drop it
to read-only and retry. Vice versa for the root filesystem; is it
mounted read-only?
Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041007/3e6e5fb8/attachment.bin
More information about the freebsd-current
mailing list