Good day,
I have renamed a ZFS dataset that contained a lot of snapshots. I just used
to rename the dataset and it looks like it worked.
Also when I list the snapshots using
, they are still all present, even with the correct names, so I was not worrying to much.
However, just for test purposes, I then tried to access one of the snapshots and was a bit shocked: When I `cd` into a snapshot, e.g.
all the files in the snapshot are not visible and it looks like the snapshot is empty!
But in `zfs list -t snap` I can clearly see that my snapshot takes some 800GB of space.
Luckily, I can manually mount the snapshot, using `mount -t zfs tank/data/newdataset@samplesnapshot /tmp/test` and this works, I can then access my snapshot data under /tmp/test. But previously, the snapshots did mount themselves automatically, and now this seems no longer to be the case, so I am wondering what is going on here? has anybody ever experienced something like this, and is it possible to fix?
I have the latest PVE version and zfs 2.2.6.
I have renamed a ZFS dataset that contained a lot of snapshots. I just used
Code:
zfs rename tank/data/mydataset tank/data/newdatasetAlso when I list the snapshots using
Code:
zfs list -t snapHowever, just for test purposes, I then tried to access one of the snapshots and was a bit shocked: When I `cd` into a snapshot, e.g.
Code:
cd /tank/data/newdataset/.zfs/snapshot/samplesnapshotall the files in the snapshot are not visible and it looks like the snapshot is empty!
But in `zfs list -t snap` I can clearly see that my snapshot takes some 800GB of space.
Luckily, I can manually mount the snapshot, using `mount -t zfs tank/data/newdataset@samplesnapshot /tmp/test` and this works, I can then access my snapshot data under /tmp/test. But previously, the snapshots did mount themselves automatically, and now this seems no longer to be the case, so I am wondering what is going on here? has anybody ever experienced something like this, and is it possible to fix?
I have the latest PVE version and zfs 2.2.6.