1 |
On Wednesday 28 March 2007, "Jeff Rollin" <jeff.rollin@×××××.com> wrote |
2 |
about 'Re: SOLVED: Recover from LVM errors? (Was: Re: [gentoo-user] Help - |
3 |
system reboots while compiling)': |
4 |
> > > 1. Frankly, I'm not impressed with Linux in this case*. /var is not |
5 |
> > > a "mission critical" filesystem in the sense that if it contains |
6 |
> > > errors, it can still be mounted and the errors don't necessarily |
7 |
> > > mean the system won't come up. |
8 |
> > |
9 |
> > [F]orcing a mount of a damaged filesystem is asking for trouble. |
10 |
> |
11 |
> It IS a bad idea, but it's not like I "forced" a mount; the system |
12 |
> came up normally and functioned normally until it hit a damaged inode, |
13 |
> whereupon it crashed with nary an indication of what had gone wrong. |
14 |
|
15 |
Ah, yes, that's a problem. What filesystem are you using? I was fairly |
16 |
sure ext2/3 tries to detect damage (even while r/w mounted) and force a |
17 |
r/o re-mount or unmount. [Not that that couldn't cause a freeze or |
18 |
reboot, but at least it's conservative.] |
19 |
|
20 |
Reiserfs (and possibly others) is quite stupid, at least in this regard. |
21 |
After the filesystem is mounted it performs basically zero sanity checks, |
22 |
and always assumes the data provided by the block device is complete and |
23 |
accurate. It can't handle a slowly failing HD, and will almost assuredly |
24 |
silently corrupt data on such a device. This is one of the reasons some |
25 |
people strongly recommend against reiserfs. I still use it, but my |
26 |
important data is on RAID6 (underneath LVM), so I can be fairly certain |
27 |
the data received by the filesystem is good. |
28 |
|
29 |
/me is looking for a new favorite file system. |
30 |
|
31 |
-- |
32 |
Boyd Stephen Smith Jr. ,= ,-_-. =. |
33 |
bss03@××××××××××.net ((_/)o o(\_)) |
34 |
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' |
35 |
http://iguanasuicide.org/ \_/ |