Date: Fri, 31 Oct 2008 06:55:40 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: Rich Winkel <rich@math.missouri.edu>, freebsd-questions@freebsd.org Subject: Re: Filesystem, RAID Question Message-ID: <490AABEC.9060107@infracaninophile.co.uk> In-Reply-To: <20081030233849.GA16747@icarus.home.lan> References: <9f3798c00810291118i1c80cb8cw8d4995eabe6a4f8f@mail.gmail.com> <4908BE2C.7010505@infracaninophile.co.uk> <20081030231207.GA56260@pencil.math.missouri.edu> <20081030233849.GA16747@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig37C731A9554B52D546D66882
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Jeremy Chadwick wrote:
> The RAID card itself may have a BBU, so during loss of power any cached=
> data *on the card* will be attempt to be flushed to disk... except the
> PC (including hard disks -- unless they're powered from some other
> source) is already down/offline by this point. And let's not forget
> that the OS/kernel is also gone, which means any writes which were
> sitting in cached memory in the kernel are lost as well.
> For some reason people think that a H/W RAID card with a BBU guarantees=
> data integrity (keyword: guarantees). I'm still trying to understand
> why people think that.
Pending writes in the BBU-backed RAM will be completed when the machine
reboots. The assumption is that the machine will be rebooted within a
few hours, before the battery runs down. Given that limitation, data
in BBU-backed cache can be regarded as committed to permanent (or more
accurately: /persistent/) storage.
Data in OS-level caches will be lost, yes. But this is the point of
softupdates. It reorders the instructions for writing data/metadata
to disk so that the data on disk remains consistent -- you may loose
some data in transit, but your disk contents will still be consistent.
Journalling achieves a similar effect in a different way -- recording
a changelog onto non-volatile storage which can later be played out to
bring the stored data into the correct state,
However, given that any access to rotating magnetic media is going to
take about 1000x longer than access to main RAM, there's always going
to be uncommitted filesystem changes in RAM that will be lost if the
machine suddenly looses power or otherwise fails. Until there is a
persistent storage medium with something like the timing characteristics
of RAM, that effect is simply unavoidable. The only strategy you can=20
employ is to provide uninterruptible power supplies, and choose hardware =
and OS wisely, so that unexpected system failures are minimized. =20
Sometimes you can benefit from having multiple machines and multiple=20
copies of your data, but this is not always possible.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
--------------enig37C731A9554B52D546D66882
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.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkkKq/MACgkQ8Mjk52CukIxEGwCgkgaTxeldyWWa2fmVTBie0b05
NjQAnjLP1u833Oxs/v8tF0Da6Mq7XQkr
=gbLB
-----END PGP SIGNATURE-----
--------------enig37C731A9554B52D546D66882--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?490AABEC.9060107>