5/31/2023 0 Comments Shadow openzfswhen I look through said mount, I now see that new files are not there, and the snapshots are taking up 0B of space, and zfs list is not showing that the used space is growing (like "du -s /pool/dataset/childDataset3" would)Īnd, if I "sudo zfs rename pool/dataset/childDataset3 pool/dataset/childDataset3-bad", the /pool/dataset/childDataset3 folder is still there with all the data, and path /pool/dataset/childDataset3-bad doesn't exist, albeit zfs thinks it exists and consuming space i.e. Note that albeit new snapshots are being made on this glitched child dataset, and I can at least mount those snapshots (albeit can't browse. Since it doesn't seem like anyone has an answer (or they do, but just not finding my post), I'll answer my question: My backup solution is to switch users to the replicated dataset (on another server), and then destroy this dataset, then send a snapshot back (but I want to avoid this, because 32TB doesn't just pop over) Using zfs version 0.7.12-2+deb10u2 if that matters So is there a way to re-create the child dataset's inode? (forgive me if I'm totally saying that wrong) I can browse one snapshot of files this way also noteworthy, when I run the disk filesystems command with show inodes, all of the working datasets and child datasets show up EXCEPT for the one I'm having trouble with (what I'm calling "childDataset3"): $ df -i zfs for them and, I can even mount a snapshot from the above list from the one troublesome dataset (so they exist, just not as a nice list in a normal spot that users can dip into): $ sudo mkdir /mnt/tempShadow I have other child datasets, and I can see the snapshot dir inside. Ls: cannot access '/pool/dataset/childDataset3/.zfs': No such file or directory $ sudo zfs list -t snapshot | grep childDataset3Ī whole bunch are listed as expected (e.g.
0 Comments
Leave a Reply. |