- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
ReadyNAS os 6.6.1 problem with snapshot
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I have problems with FW:6.6.1
I saw in logs that snapshots are not created for one share. So I was trying to make manual one, and i get error
Code .28003020001
This share is compressed with SMB and RSYNC access.
Any ide what is wrong, what this error means?
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
that is what I did to solve it
snapper list-configs
Config | Subvolume
-------+-------------------------
0 | /data/*-old
/etc/snapper/configs
remove 0 (or copy it, number from the list)
reboot
after reboot
from web interface remove share, this time will go.
I am was not sure if this is fine, so
I recreate share from web interface
snapper list-configs
this time this share get nex number 5.
So, I remove share and I have a hope that this is it.
New snapshots are working fine.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
Hi Alein,
I may need to inquire about the error code.
Just to isolate, when you try to manually create snapshot on a newly created shares; it works?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
Hi,
manual is not working, auto is not working.
For new share it is working fine with this same settings, and of course for all other shares.
I solve this problem creating new share. But I do not know if this problem will return or not, that is why I would like to know what this error means. It will takes some time until I will have full copy of my previous share ( it is almost 1TB of compressed data with 1M files, so I am copying files slowly without impact on production)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
Problem is, what this error means, not if I can or can not do something. You are posting your questions not answering my 🙂
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
Can you send in your logs (see the Sending Logs link in my sig)? In your email please also mention which share you are having this problem on.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
Thanks for the logs. I've sent you a PM.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
Seeing you're unable to provide remote access there's not much more I can do. That share is not setup properly to have snapshots on it. So my proposal was to remotely fix it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
I can not allow you to access, due to nature of the data.
Please tell me what is wrong with this share, so next time I will fix it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
@Alein wrote:
I can not allow you to access, due to nature of the data.
Perhaps you can create a new share with snapshots enabled. After confirming that the snapshots are working, you can move the data from the current share into the new one, and then delete the old share.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
It seems that this is not the end of my problem with this share.
I can not delete it.
Any suggestions?
PS.there are not snapshots of this share at all.
I check it with.
root@iSCSI-NAS:~# btrfs subvolume list /data -s
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
The snapper config of the share is broken.
What happens if you do
# snapper -c 0 delete-config
We use the number 0 in this case because
# snapper list-configs
shows that the share has config # 0.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
That is what I get.
I use * to hide shares names.
Welcome to ReadyNASOS 6.6.1
Last login: Sat Mar 4 22:57:54 2017 from 172.26.12.230
root@iSCSI-NAS:~# snapper list-configs
Config | Subvolume
-------+-------------------------
0 | /data/R*-old
1 | /data/E*
3 | /data/S*
4 | /data/R*
root@iSCSI-NAS:~# snapper -c 0 delete-config
Deleting config failed (deleting snapshot failed).
root@iSCSI-NAS:~#
And I made list of all snapshots
root@iSCSI-NAS:~# btrfs subvolume list /data/
ID 257 gen 35347 top level 5 path .purge
ID 258 gen 49621 top level 5 path ._share
ID 259 gen 49607 top level 5 path .apps
ID 260 gen 35347 top level 5 path home
ID 261 gen 35347 top level 5 path .vault
ID 263 gen 49687 top level 5 path ESXi
ID 264 gen 49606 top level 5 path .timemachine
ID 265 gen 49680 top level 263 path ESXi/.snapshots
ID 266 gen 48986 top level 5 path F*
ID 267 gen 49684 top level 266 path F*/.snapshots
ID 268 gen 49613 top level 5 path R*-old
ID 269 gen 48992 top level 5 path Stations-Backup
ID 270 gen 49687 top level 269 path Stations-Backup/.snapshots
ID 279 gen 35347 top level 260 path home/*/administrator
ID 2646 gen 49620 top level 5 path R*t-Backup
ID 2647 gen 49683 top level 2646 path R*t-Backup/.snapshots
ID 3107 gen 47299 top level 265 path ESXi/.snapshots/256/snapshot
ID 3114 gen 47690 top level 265 path ESXi/.snapshots/257/snapshot
ID 3131 gen 48249 top level 265 path ESXi/.snapshots/258/snapshot
ID 3147 gen 48983 top level 265 path ESXi/.snapshots/259/snapshot
ID 3149 gen 48986 top level 267 path F*/.snapshots/7/snapshot
ID 3151 gen 48992 top level 270 path Stations-Backup/.snapshots/8/snapshot
ID 3155 gen 49614 top level 265 path ESXi/.snapshots/260/snapshot
ID 3156 gen 49616 top level 2647 path R*-Backup/.snapshots/13/snapshot
ID 3157 gen 49618 top level 265 path ESXi/.snapshots/261/snapshot
ID 3158 gen 49620 top level 2647 path R*-Backup/.snapshots/14/snapshot
root@iSCSI-NAS:~#
Will it be safe to delete this snapshot?
ID 268 gen 49613 top level 5 path R*-old
btrfs subvolume delete R*-old
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
That's the wrong path to delete the share. What's missing if I recall correctly is the .snapshots subvolume for the share.
So one option is to manually remove the snapper config for the share and then recreate this. I can easily fix this remotely, but if you try it yourself I'm concerned you might break your snapper config for your other shares.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
Dear Sir,
when i updated the firmware version to 6.6.1, The system cannot take snapshot and then show the error.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS os 6.6.1 problem with snapshot
I made a copy of data and
root@iSCSI-NAS:~# btrfs subvolume delete RezDent-Backup-old
ERROR: cannot access subvolume RezDent-Backup-old: No such file or directory
root@iSCSI-NAS:~#
I can not remove this snapshot.
Can you provide me a way to solve it?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
that is what I did to solve it
snapper list-configs
Config | Subvolume
-------+-------------------------
0 | /data/*-old
/etc/snapper/configs
remove 0 (or copy it, number from the list)
reboot
after reboot
from web interface remove share, this time will go.
I am was not sure if this is fine, so
I recreate share from web interface
snapper list-configs
this time this share get nex number 5.
So, I remove share and I have a hope that this is it.
New snapshots are working fine.