Skip to main content

Can ext4 fs be completely unrecoverable broken due to power loss while disk is writing?

itemprop="text">

Suppose you are doing a full speed
write to disk in a linux pc box with ssd or mechanical disk (OS also on the same disk,
there is no battery/UPS):



cat
/dev/urandom >
omg.txt


If the power
losses suddenly during the process, or any other sort of ungracefully
shutdown/reset.




Will the file be
corrupted and unable to fix (i.e. none of any data can be recovered?), will there be a
chance the file system be completely unable to boot?



Answer





Will the file be corrupted and unable to fix
(i.e. none of any data can be
recovered?)




Potentially,
yes. There's 2 obvious routes via which this could
happen.



Ext4 is a metadata journaling filesystem
- it only journals the changes to the file's meta data (size, location, dates) - not the
file contents (btrfs and zfs do full-data journalling at a big performance cost). So
although you should never have to fsck the disk, it doesn't follow that every write
operation betwen opening the file and closing + flushing the buffers will have
completed. There is no transactional control over writes to the file
data.




A second possibility is that
the disk may be physically damaged by power spikes. Although the rest of the hardware
tends to do a good job of isolating the hard disk, there will still be some
leakage.




will
there be a chance the file system be completely unable to
boot?




That's a
very different question - this is a lot less likely. Certainly the first scenario only
applies if you happen to be writing the kernel, bootloader, ramdisk etc at the time of
the outage.



See also href="https://unix.stackexchange.com/questions/12699/do-journaling-filesystems-guarantee-against-corruption-after-a-power-failure">this
Q&A on unix.stackexchange




Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able