Date: Thu, 20 Oct 2011 14:30:03 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-questions@freebsd.org Subject: Re: Bad sector in UFS2 journal area Message-ID: <j7p48i$lce$1@dough.gmane.org> In-Reply-To: <CANmv3=w_gvvJRZRHa8e5F9G4VCY4aiJDJmjfHLqMMH6X3WUGyQ@mail.gmail.com> References: <CANmv3=w_gvvJRZRHa8e5F9G4VCY4aiJDJmjfHLqMMH6X3WUGyQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFA59B64FA634378E4560A37E Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 20/10/2011 05:49, Ross wrote: > I don't actually have this problem, I'm just curious. What will happen > if read fails on sector in UFS2 journal area? Sector won't get > remapped until write, so reads will be failing until then. >=20 > I've had experience with bad sectors with non-journaled filesystems =E2= =80=94 > the system was online and working. The only problem was that > particular file and messages in /var/log/messages until the Current > Pending Sector counter was cleared and sector was remapped. >=20 > Will it be the same (online system) with bad sector in journal area? > And will it damage the filesystem? Well, SUJ is new enough that there's no general disseminated knowledge about it, but from a quick look at the code: 1) the journal recovery is only ever done in the fsck_ffs program, so it's unlikely that the kernel will panic from a bad sector 2) if the journal cannot be read at any point, the recovery code *should* offer the user to nuke the journal and perform a normal, full fsck, which presumably should leave the file system in a usable state 3) journal writes are done via the normal mechanisms, so it also shouldn't lead to kernel panics on bad sectors, but the "normal" cannot-write-to-device kernel error message and continued operation. --------------enigFA59B64FA634378E4560A37E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6gFFIACgkQldnAQVacBcgiGgCgmOM7FSrCv6/oTc5Butmb/66P CywAoOi15hQ53vWj6PKCSRl8JT7vclAW =E8MJ -----END PGP SIGNATURE----- --------------enigFA59B64FA634378E4560A37E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?j7p48i$lce$1>