Prev: NYC LOCAL: Tuesday 19 January 2010 Perl Seminar NY: Kristina Chodorow on MongoDB
Next: photo display engine for Linux: alternatives to picassa flickr etc.
From: Ryan Chan on 19 Jan 2010 10:07 Hi, Can a ext3 filesystem corrupt due to power failure?
From: Stan Bischof on 19 Jan 2010 10:20 Ryan Chan <ryanchan404(a)gmail.com> wrote: > Hi, > > Can a ext3 filesystem corrupt due to power failure? Of course-- hard power failure can corrupt just about anything. However the whole idea of a journaling system like ext3 is that it becomes much more resistant to such corruption. Even after a nasty event an fsck should take care of things. If you have frequent power problems then a UPS and an automated shutdown routine linked to the UPS are extremely valuable. And obviously backups are needed for anything you care about. Stan
From: J G Miller on 19 Jan 2010 11:12 On Tue, 19 Jan 2010 15:20:14 +0000, Stan Bischof wrote: > However the whole idea of a journaling system like ext3 is that it > becomes much more resistant to such corruption. Even after a nasty event > an fsck should take care of things. If the journal is in the process of being updated at the time of the power failure, recovery become a little more difficult when the message "Invalid argument while checking ext3 journal" appears.
From: The Natural Philosopher on 19 Jan 2010 12:42 Ryan Chan wrote: > Hi, > > Can a ext3 filesystem corrupt due to power failure? any fil4system can. Most typcally during times of high disk activity. The very worst time to have power goi down is when yiur autoooting machine has gione down because teh power went out, and the automatic power restoration cutss in, to find there is STILL a tree across the lines, and just as you are loading the kernel and the boot sector CRASH. down goes the head and bye bye disk and any chance of recovering it.
From: The Natural Philosopher on 19 Jan 2010 12:46
J G Miller wrote: > On Tue, 19 Jan 2010 15:20:14 +0000, Stan Bischof wrote: > >> However the whole idea of a journaling system like ext3 is that it >> becomes much more resistant to such corruption. Even after a nasty event >> an fsck should take care of things. > > If the journal is in the process of being updated at the time of the > power failure, recovery become a little more difficult when the message > > "Invalid argument while checking ext3 journal" > > appears. Precisement mon cher. IF uyou have a machine, even if it is a server NEVER set it to auoboot on power restoration. 99% of ALL our outages are of the down, up, down, up , stay down or stay up variety. A total nightmare. Lost two machines and had a hard time with a third over the years,. Not lost one at all with go don stay down approaches. The other ghastliness is the branch just touching the wires --brownouts. Machine goes down, comes up and next time BANG the branch REALLY shorts the thing..just as its doing its fsck from the last crash..no..dont go there.. |