summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
Diffstat (limited to 'README')
-rw-r--r--README8
1 files changed, 4 insertions, 4 deletions
diff --git a/README b/README
index 19140ea..8c7e6ec 100644
--- a/README
+++ b/README
@@ -232,12 +232,10 @@ This works only correct for a limited time if you continue to write into the fil
Problems still exist with some multimedia formats and some documents. Not every file type
can be restored only based on head and foot patterns. Some types of multimedia streams, splited or
- truncated files are hard to recover. We are working hard on this problem, and in newer versions is the support
- for these file types are much better.
+ truncated files are hard to recover. We are working hard on this problem, and in newer versions is the support for these file types are much better.
The recovery of CD/DVD images and other file system containers is also problematic. This can only work
in file systems with 4KB block size.
- Sparse files, and very large files if not deleted in one step, can not be restored with this
- function. (Bug:#017607)
+ on ext3 very large files if not deleted in one step, can not be restored with this function. (Bug:#017607)
Of course, you can only find files when the "file" command recognize this file type. It is theoretically
possible to enable the restore of unknown file types by an entry in the configuration file to "magic".
@@ -512,6 +510,8 @@ two possible causes:
libext2fs-1.42 has a small bug, it crashed ext4magic. (see e2fstools BUG #3451486)
+
+
Only on big endian environments, there are some incorrect outputs of inode times, and missing of
deleted directory entries. (BUG #017304 #017305)
These errors occur only if the journal is not read and so only called the functions of libext2fs for