Date: Wed, 18 Apr 2007 23:37:17 +0200 From: Roland Smith <rsmith@xs4all.nl> To: CyberLeo Kitsana <cyberleo@cyberleo.net> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: dump/restore corrupted filesystems Message-ID: <20070418213717.GB74368@slackbox.xs4all.nl> In-Reply-To: <46268919.1080301@cyberleo.net> References: <4623843B.40006@cyberleo.net> <20070416170825.GA91459@slackbox.xs4all.nl> <462449C2.9000302@cyberleo.net> <20070416222437.GA1924@slackbox.xs4all.nl> <46268919.1080301@cyberleo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--7iMSBzlTiPOCCT2k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 18, 2007 at 04:09:22PM -0500, CyberLeo Kitsana wrote: > Roland Smith wrote: > >> Sorry if I wasn't clear. Most all of the data is readable and complete > >> if I mount the filesystem read-only. It just panics the box when mount= ed > >> read/write, and fsck can't fix the damage. > >=20 > > That might be worth filing a PR for, especially the panics.=20 > >=20 > > Exactly what is damaged? Garbage in files? Wrong inode counts? I've had > > unclean filesystems because of panics, but nothing fsck_ffs couldn't > > fix. > >=20 > > You might want to check the hardware too. Use smartmontools in case of > > (S)ATA drives. >=20 > Smart says that the drives are fine, as does the manufacturer's disk > fitness tools. That's at least some good news. > --8<-- > rsync: readlink > "/raid/Backup/Pizzabox/2007-02-23/cyberleo/secondlife/linux/SecondLife_i6= 86_1_13_2_15/skins/xui/es" > failed: Bad file descriptor (9) > rsync: readlink > "/raid/Backup/Pizzabox/2007-02-23/cyberleo/secondlife/linux/SecondLife_i6= 86_1_13_2_15/skins/xui/fr" > failed: Bad file descriptor (9) > --8<-- At least these files should be easy to replace, if necessary. > fsck_ufs dies after about 30 minutes of grinding with the following: >=20 > --8<-- > ** Phase 2 - Check Pathnames > DIRECTORY CORRUPTED I=3D93409222 OWNER=3D1002 MODE=3D40755 > SIZE=3D512 MTIME=3DFeb 10 00:49 2007 > DIR=3D? >=20 > UNEXPECTED SOFT UPDATE INCONSISTENCY Did these problems start after a crash?=20 > SALVAGE? no What happens if you tell it to try and salvage? =20 Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --7iMSBzlTiPOCCT2k Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGJo+NEnfvsMMhpyURApSaAKCTIa+xdYri/rc7hQ72iW/Rg4GdNgCeKZq+ VL3Y0eKPyY//PenzpZ4vsac= =7L0M -----END PGP SIGNATURE----- --7iMSBzlTiPOCCT2k--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070418213717.GB74368>