summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorrobi <robi>2011-06-01 00:48:07 +0000
committerrobi <robi>2011-06-01 00:48:07 +0000
commitfe600c96a9d3303b68945da4aa333b6451775fb8 (patch)
tree1a8b0102a4e39afea6e11b2defebc97fcd90790e
parentd9f1d6a97d8b8c522d2d9a1983050d166980b74c (diff)
small addition
-rw-r--r--README5
1 files changed, 3 insertions, 2 deletions
diff --git a/README b/README
index 1cc6b67..4c128a7 100644
--- a/README
+++ b/README
@@ -352,15 +352,16 @@ In the combination of all these options, you can try a file system restore if th
and the beginning of the file system is corrupted or overwritten.
Repair with e2fsck is often possible, but risky for large damage, ext4magic here often has better
-chances of success. In the comparison the two commands:
+chances of success. But, this can only work before a repair was attempted with e2fsck.
+In the comparison the two commands:
# repair an ext3 file systems with broken superblock
fsck.ext3 -B 4096 -b 32768 -y -f /dev/sda1
-# ext4magic file system restore, write to /tmp/recover
+# ext4magic file system restore, write to /tmp/recover
ext4magic /dev/sda1 -s 4096 -n 32768 -c -D -d /tmp/recover