svn commit: r1400747 - /subversion/trunk/notes/fsfs

[da...@apache.org]

Author: danielsh
Date: Mon Oct 22 01:35:27 2012
New Revision: 1400747

URL: http://svn.apache.org/viewvc?rev=1400747&view=rev
Log:
* notes/fsfs: Document another solution to the problem documented in r1400746.

Suggested by: breser

Modified:
    subversion/trunk/notes/fsfs

Modified: subversion/trunk/notes/fsfs
URL: http://svn.apache.org/viewvc/subversion/trunk/notes/fsfs?rev=1400747&r1=1400746&r2=1400747&view=diff
==============================================================================
--- subversion/trunk/notes/fsfs (original)
+++ subversion/trunk/notes/fsfs Mon Oct 22 01:35:27 2012
@@ -241,8 +241,8 @@ will raise an error when accessed.  'svn
 establishing an appropriate SQLite lock (see svn_sqlite__hotcopy()).  User
 code should either use an atomic filesystem snapshot (as with zfs/LVM),
 refrain from copying rep-cache.db, or stop all access to that file before
-copying it (either by disabling commits or by establishing a lock a la
-svn_sqlite__hotcopy()). ]
+copying it (for example, by disabling commits, by establishing a lock a la
+svn_sqlite__hotcopy(), or by using 'svnadmin freeze'). ]
 
 The "svnadmin hotcopy" command avoids this problem by copying the
 "current" file before copying the revision files.  But a backup using