Bug #6930
closedFolders report "Not a folder" in Kernel 3.13-rc1 and -rc2
0%
Description
Seems to be a regression in the 3.13-rc1 and -rc2 kernels
When you mount a filesystem is mounts fine. dmesg is clean
You can cd into the mount point but to move into folders below that you get the "Not a folder" error.
As you can see in the below ls the folders are reporting somewhat correctly.
root@linux-549s { /home/malcolm/Ceph }# ls -la
total 16K
drwxrwxr-x 1 malcolm 1000 1.8T Dec 4 20:21 ./
drwxr-xr-x 150 malcolm users 12K Dec 4 20:22 ../
drwxr-xr-x 1 root root 104G Nov 24 00:38 Photos/
drwxr-xr-x 1 root root 0 Nov 23 22:22 test/
drwxr-xr-x 1 root root 0 Dec 4 20:21 test2/
drwxrwxrwx 1 root root 1.7T Nov 25 23:43 videos/
Creating new folders is possible
root@linux-549s { /home/malcolm/Ceph }# mkdir test3
root@linux-549s { /home/malcolm/Ceph }# ls -la
total 16K
drwxrwxr-x 1 malcolm 1000 1.8T Dec 4 20:49 ./
drwxr-xr-x 150 malcolm users 12K Dec 4 20:22 ../
drwxr-xr-x 1 root root 104G Nov 24 00:38 Photos/
drwxr-xr-x 1 root root 0 Nov 23 22:22 test/
drwxr-xr-x 1 root root 0 Dec 4 20:21 test2/
drwxr-xr-x 1 root root 0 Dec 4 20:49 test3/
drwxrwxrwx 1 root root 1.7T Nov 25 23:43 videos/
But actually using new folders
root@linux-549s { /home/malcolm/Ceph }# cd test3
bash: cd: test3: Not a directory
Doesn't work.
I can roll back to a stable 3.12 so its not an issue but I figured I'd raise a bug about it as it is one.