My arrangement is two subvolumes, 'root' and 'home', directly under the root
subvolume. The 'root' subvolume is mounted on /, the 'home' subvolume on /home.
I've tried both pointing the find command at /, and mounting the root subvolume
on a mount directory and pointing it there. Neither show any file or directory
with inum 515.
On Sun, Jan 24, 2016 at 02:07:58PM -0700, Chris Murphy wrote:
> On Sun, Jan 24, 2016 at 1:58 PM, Tom Hunt <tomdicksonhunt@xxxxxxxxx> wrote:
> >> You delete the file and yet the scrub still says inode 515 exists and
> >> has an error? Or there are no errors, but then after copying the same
> >> file back to the volume, the problem reoccurs? Are there any snapshots
> >> or subvolumes? Because if there are any subvolumes/snapshots, each is
> >> its own fs tree with its own set of inodes. So an inode can be used
> >> more than once for different files so I wonder off hand if you haven't
> >> found the actual problematic file.
> >>
> >> Or possibly it's a directory, and not a file.
> >
> > There are no snapshots, but there are subvolumes. I did the same procedure on
> > the file at inode 515 in each subvolume, which was:
> >
> > # cp $file ~
> > # rm $file
> > # mv ~/$file {old_file_path}
> >
> > This concluded without any errors. After doing this, the inode number is
> > different, and 'find / -inum 515' no longer finds anything on either subvolume.
> > However, initiating a scrub after this still shows the error at ino 515.
>
> Try pointing the find command at the mountpoint, rather than at a subvolume.
>
>
> --
> Chris Murphy
--
Tom Hunt
--
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
