diff options
author | Ulrich Spörlein <uqs@FreeBSD.org> | 2010-10-31 19:16:54 +0000 |
---|---|---|
committer | Ulrich Spörlein <uqs@FreeBSD.org> | 2010-10-31 19:16:54 +0000 |
commit | ec1e236534b5395cb36f7b3dee6f902a02bfd42a (patch) | |
tree | 69cbbdd4c947902f3b67f9fc20834261cd447fca /bin/rm | |
parent | 50fd2a5b9c3463b547e6556de2725b27fa0123c7 (diff) | |
download | src-test2-ec1e236534b5395cb36f7b3dee6f902a02bfd42a.tar.gz src-test2-ec1e236534b5395cb36f7b3dee6f902a02bfd42a.zip |
Notes
Diffstat (limited to 'bin/rm')
-rw-r--r-- | bin/rm/rm.1 | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bin/rm/rm.1 b/bin/rm/rm.1 index 4e4f240b0f14..ad8106617aca 100644 --- a/bin/rm/rm.1 +++ b/bin/rm/rm.1 @@ -234,12 +234,12 @@ command appeared in .Sh BUGS The .Fl P -option assumes that the underlying storage overwrites file block +option assumes that the underlying storage overwrites file blocks when data is written to an existing offset. Several factors including the file system and its backing store could defeat this assumption. This includes, but is not limited to file systems that use a Copy-On-Write strategy (e.g. ZFS or UFS when snapshots are being used), Flash -media that is using a wear leveling algorithm, or when the backing datastore +media that are using a wear leveling algorithm, or when the backing datastore does journaling, etc. In addition, only regular files are overwritten, other types of files are not. |