On 2017-02-26 14:45, jdd wrote:
Le 26/02/2017 à 13:07, Carlos E. R. a écrit :
If a root fs is broken, whom will you ask to fix anything if the tools available are simply disfunctional?
Well, ask here. :-)
exactly :-)
The snag is, you need a working computer and wait several days with a broken computer.
But you are right, the tools should work, automatically, and never make things worse.
It's debatable, what tool? I was *always* instructed since 20 years ago *not* to use fsck without knowing exactly what to do, as it's right for dd or some other very lowlevel tool.
One tool. The first thing I do with any filesystem that I suspect is broken, is fsck it. Always. On some, like XFS, that program does nothing and tells me what other program to use, and that other tool works on most cases out of the box. It it doesn't, it recommends what to do next: typically run it again with some option. If all that fails, then email the XFS support mail list. In most of my cases, I had found a new bug, or it was an already known bug which required a new version of the repair tools, already built for openSUSE in the expected repo.
Reboot, choose a previous snapshot, problem
solved. In minutes.
not solved at all (no space left on device). Works when the problem come from kernel or similar
Well, you must never get close to no space on btrfs.
It has compression. I have not tried it yet, but it is the only r/w Linux filesystem that has it. NTFS has it, since ages.
I challenge the need with so large mass storage - most large files I know are photo or video and they don't compress well (already natively compressed)
Well, it irks me not to use compression on things that can use it. For instance, email and news. Big and/or many text files. Backups are often compressed: tgz, zip, rar... I could instead use rsync on a compressed destination disk. Or dd, many empty sectors. But I can't trust it! :-( -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))