- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Snapshot count and protection duration in share overview page wrong
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Snapshot count and protection duration in share overview page wrong
I have a ReadyNAS 3312 with firmware version 6.9.3 with multiple shares. On all shares, daily snapshots are enabled, which I store at least two weeks. Now, with one share the displayed snapshot count and especially the protection duration is totally wrong:
I had to black-out the real share names
The real snapshot count for Share 2 is 12, as seen in the snapshot overview:
I suspect the 13th snapshot is causing the problem with the wrong proctection duration, however, I can't find it. I already deleted all snapshots for this share and let them recreate, without luck. The count for Share 1 aswell as all the other shares is correct.
Checking the snapshots in the filesystem over SSH in /data/share2/snapshots/ I can't find the 13th snapshot aswell.
Is this a result of a bug or why is there a invisible snapshot?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Snapshot count and protection duration in share overview page wrong
How old is the data volume? There have been some firmware updates in the past that needed to convert snapshots. Sometimes they didn't convert all of them, and that resulted in some "invisible" snapshots.
Since you have ssh enabled, try entering
# btrfs subvolume list /data
That will give you the full subvolume list (all shares, including their snapshots) - which should allow you to find the old one. There is also a btrfs command that would let you delete that snapshot ( btrfs subvolume delete <pathname> ). You do need to be careful to enter that one correctly, as you don't want to accidently delete the main share.
Another approach is to create a new share, copy the contents of the share2 into it, and then delete share2 from the web ui. You can then use the command above to confirm that the snapshots for share2 are all gone. And of course you can rename the new share to share2.