Date: Thu, 7 Oct 2004 06:34:15 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Chris Elsworth <chris@shagged.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: dump/mksnap_ffs & fsck failure Message-ID: <20041007133415.GA93146@xor.obsecurity.org> In-Reply-To: <20041007110802.GA4960@shagged.org> References: <20041007110802.GA4960@shagged.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBZUXWWry0BWjoQKURAtCQAKDXTLZw7s9y/Y4oaIz/VDNLmcoKHwCgqTlZ RQq6ztN/aGnmIGMnCoFcew0= =DJ35 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041007133415.GA93146>