diff options
| author | Jim Meyering <jim@meyering.net> | 2005-06-17 13:16:00 +0000 |
|---|---|---|
| committer | Jim Meyering <jim@meyering.net> | 2005-06-17 13:16:00 +0000 |
| commit | 0a0ebe7a41792e71e725e619b86266121e306da6 (patch) | |
| tree | 5eb5aa9e0d71e49a037477e9e8c9fa930dc2db43 /src/shred.c | |
| parent | fd684a32fde6a449332ef9e5351a0db7f5c54f5d (diff) | |
| download | coreutils-0a0ebe7a41792e71e725e619b86266121e306da6.tar.xz | |
(usage): Clarify that shred works on an ext3 file
system as long as it's not in data=journal mode.
Tiny change by Mark Melahn.
Diffstat (limited to 'src/shred.c')
| -rw-r--r-- | src/shred.c | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/src/shred.c b/src/shred.c index 02b975101..90e47d7f0 100644 --- a/src/shred.c +++ b/src/shred.c @@ -190,7 +190,7 @@ CAUTION: Note that shred relies on a very important assumption:\n\ that the file system overwrites data in place. This is the traditional\n\ way to do things, but many modern file system designs do not satisfy this\n\ assumption. The following are examples of file systems on which shred is\n\ -not effective:\n\ +not effective, or is not guaranteed to be effective in all filesystem modes:\n\ \n\ "), stdout); fputs (_("\ @@ -209,6 +209,14 @@ not effective:\n\ \n\ * compressed file systems\n\ \n\ +In the case of ext3 filesystems, the above disclaimer applies\n\ +(and shred is thus of limited effectiveness) only in data=journal mode,\n\ +which journals file data in addition to just metadata. In both the\n\ +data=ordered (default) and data=writeback modes, shred works as usual.\n\ +Ext3 journaling modes can be changed by adding the data=something option\n\ +to the mount options for a particular file system in the /etc/fstab file,\n\ +as documented in the mount man page (man mount).\n\ +\n\ In addition, file system backups and remote mirrors may contain copies\n\ of the file that cannot be removed, and that will allow a shredded file\n\ to be recovered later.\n\ |