[TriLUG] How to prevent? "fsck died with exit status 4"

[Joseph Mack NA3T]

On Sun, 28 Sep 2014, Jeremy Davis wrote:

> After reading up on the file system journalling, I suspect this is missing
> from AV Linux and may be causing the recovery problems after a sudden
> shutdown. It may have been removed or left out to improve latency when
> recording.

if so it's a dangerous thing to do. Presumably what you're doing is a bit of 
work and you can _never_ jeapardise your files. If they're relying on not having 
journalling then it hasn't been designed right.

Are you running out of memory when the machine crashes? Can you make it crash on 
demand by flogging your audio app? Watch with  `top` and look at swap etc. Maybe 
you could handle more writes by adding more memory. This will give a bigger 
cache for writes. Memory is dirt cheap.

assuming your disk is OK, then you need to find out why you have unexpected 
shutdowns. Is it your RT app? Is it the disk system (get a disk exerciser and 
beat your disk to death)?

> If filesystem journalling is not present, I wonder if working off the live
> cd might be the best way to go, with an external drive for the Ardour files
> etc.. Hopefully a sudden shut down would not corrupt the external drive.

If your audio files are being written when the machine crashes, then they (and 
if you don't have journalling, the filesystem) will be corrupted no matter where 
you write them.

You need to find the problem before you can think of a solution.

o the disk/harware

o your RT application (including a requirement to run without journalling).

Joe

-- 
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!