On Oct 24, 2013, at 9:29 AM, Karl Kiniger <karl.kiniger@xxxxxxxxxx> wrote: > Dear list, (newbie alert) > > After sucessfully sending and receiving a dozen of related snapshots > I want to move them all to the readonly folder but I cannot: > > ls -l > ..... > drwxr-xr-x. 1 root root 682 Oct 24 16:01 @20131001 > drwxr-xr-x. 1 root root 682 Oct 24 16:07 @20131004 > drwxr-xr-x. 1 root root 682 Oct 24 16:10 @20131008 > drwxr-xr-x. 1 root root 682 Oct 24 16:16 @20131010 > drwxr-xr-x. 1 root root 682 Oct 24 16:23 @20131014 > drwxr-xr-x. 1 root root 706 Oct 24 16:24 @20131018 > drwxr-xr-x. 1 root root 706 Oct 24 16:31 @20131021 > drwxr-xr-x. 1 root root 734 Oct 24 16:36 @20131023 > drwxr-xr-x. 1 root root 734 Oct 24 16:41 @20131024 > drwxr-xr-x. 1 root root 734 Oct 24 16:41 F19 > drwxr-xr-x. 1 root root 0 Oct 24 17:21 readonly > > > mv \@20131024 readonly > > mv: cannot move ‘@20131024’ to ‘readonly/@20131024’: Read-only file system Are the @ snapshot read only snapshots? And is read only just a regular directory? I don't know that this is a bug, it seems like it could be intentional because a read only file system wouldn't let you move it out of one tree into another. But there was a bug that prevented moving of subvolumes into subvolumes (untested if moving subvolumes into folders worked) that was fixed in kernel 3.11.6 so that might be worth a shot. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
