Bug in unify rename

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

If you attempt to rename a file on a unify subvolume that is unavailable,
the operation will fail, however the file in the namespace will be renamed
regardless. When the volume comes back online, the old file will be self-healed
back into the namespace, and the renamed file will not be present on any
subvolumes.

For example:
[file /clusterfs/foo exists on a currently inaccessible volume and in
the namespace]

# mv /clusterfs/foo /clusterfs/bert
mv: cannot move `/clusterfs/foo' to `/clusterfs/bert': No such file or directory
[exitstatus = 1]

-- Sam Douglas




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux