diff --git a/help/C/gparted.xml b/help/C/gparted.xml index 3748d5fd..ffc88fd8 100644 --- a/help/C/gparted.xml +++ b/help/C/gparted.xml @@ -1,9 +1,9 @@ - - + + + + + &appname; Manual V1.4 + February 2012 + + Curtis Gedak + &appname; Project + Describes version 0.12.0 of &appname; + + &appname; Manual V1.3 January 2011 @@ -1668,27 +1677,48 @@ as the source partition. This can cause a problem when mount actions use the partition label or the UUID to identify the partition. - The problem is that the label and the UUID are not unique. - You are advised to do one of the following: + The problem is that the operating system will randomly + select to mount either the source, or the copy of the + partition. For example, on the first mount action the + source partition might be mounted. On the next mount action + the copy of the partition might be mounted. Over time this + random nature of partition mounting might make files seem to + mysteriously appear or disappear depending upon which + partition is mounted. + + + To avoid the problem you are advised to do one of the + following: - Change the UUID of the partition. - See . - - - If the partition label is not blank, change the label - of the partition. - See . + After you have applied the copy operation: + + + + Change the UUID of the partition. + See . + + + + + If the partition label is not blank, change the + label of the partition. + See . + + + Use some other method to ensure that the source - partition and the copy of the source partition - are not used on the same computer at the same time. + partition and the copy of the partition are not used + on the same computer at the same time. For example, + if the copy of the partition is on a separate drive + then remove the drive from the computer.