> Hi all, > > When I am creating subvolumes I get this strange behavior. If I create > a subvolume with a name longer than 4 characters it is read-only, if > the name is shorter than 5 characters the subvolume is writeable as > expected. I think it is since I upgraded to kernel version 2.6.38 (I > do not create subvolumes on a regular basis.). I will compile one of > the latest 2.6.37 kernels to see whether there the problem exists, > too. Another interesting point is that previously created subvolumes > are not affected. > > Thanks, > Andreas Philipp > > thor btrfs # btrfs subvolume create 123456789 > Create subvolume './123456789' > thor btrfs # touch 123456789/lsdkfj > touch: cannot touch `123456789/lsdkfj': Read-only file system This is really odd, but I can't reproduce it. I created a btrfs filesystem on 2.6.37 kernel, and rebooted to latest 2.6.38+, and tried the procedures as you did, but nothing bad happend. -- 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
