- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Deleting Redundant Time Machine Backup v2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
After recovering failed btrfs due to a hard reset (many thanks again to StephenB!) I ran into issues with TimeMachine backups. I am looking to remove the old backups (this was very helpful https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Deleting-Redundant-Time-Machine-Bac...) but am not sure which path I need to include in the following ssh command
# btrfs subvolume delete -c /path
I thought it should be /data/.timemachine, but it does not seem to work. The subvol list/data gives the following for TM
ID 265 gen 886902 top level 5 path .timemachine
TIA
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
If you are wanting to delete all the backups in the .timemachine folder, you should be able to just navigate into it and delete the the backups there (leaving .timemachine itself alone).
I'm not a mac user, but I believe you should also be able to delete the backups from the mac.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Do I navigate to the .timemachine folder via ssh? I would appreciate an instruction on how to do it. Otherwise, I am unable to access this folder using
http[s]://[NAS]/admin/browse.html#path=%2Fdata%2F.timemachine.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Since losing the btrfs file system, I am getting error messages when trying to connect to the folder using smb. I figured my best bet would be to delete all prior backups (I have 1 actually) and then reconfigure the TM from scratch.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
One way to as access the full NAS data volume (\\nas-ip-address\data ) using the NAS admin credential. .timemachine is a hidden folder, so you would need to enable viewing that.
With ssh, you'd enter
cd /data/.timemachine
to navigate into the .timemachine folder
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Unfortunately, I am getting an error message:
root@NASHNAS:~# cd /data/.timemachine
-bash: cd: /data/.timemachine: Input/output error
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
@vasyam wrote:
Unfortunately, I am getting an error message:
root@NASHNAS:~# cd /data/.timemachine
-bash: cd: /data/.timemachine: Input/output error
That works on my system.
Do you see the folder if you enter this:
# ls -al /data/ | grep -i .timemachine
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Here is what I am getting:
root@NASHNAS:~# cd /data/.timemachine
-bash: cd: /data/.timemachine: Input/output error
root@NASHNAS:~# # ls -al /data/ | grep -i .timemachine
root@NASHNAS:~#
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
@vasyam wrote:Here is what I am getting:
root@NASHNAS:~# cd /data/.timemachine
-bash: cd: /data/.timemachine: Input/output error
root@NASHNAS:~# # ls -al /data/ | grep -i .timemachine
root@NASHNAS:~#
I was not sure of the hash, without it the error looks the following:
root@NASHNAS:~# ls -al /data/ | grep -i .timemachine
ls: cannot access '/data/.timemachine': Input/output error
d?????????? ? ? ? ? ? .timemachine
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
You're not supposed to enter the hash.
What happens if you simply do an ls -al /data
Do you still see an Input/output error?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
@StephenB wrote:You're not supposed to enter the hash.
What happens if you simply do an ls -al /data
Do you still see an Input/output error?
Here is what I am getting:
root@NASHNAS:~# ls -al /data
ls: cannot access '/data/.timemachine': Input/output error
total 64
drwxr-xr-x 1 root root 188 Oct 10 21:47 .
drwxr-xr-x 1 root root 198 Mar 16 2020 ..
drwxrwxr-x 1 root root 168 Oct 10 23:11 .apps
-rwxrwxr-x+ 1 admin admin 8196 Oct 4 00:51 .DS_Store
drwxr-xr-x 1 admin admin 28 Oct 4 00:28 home
drwxrwxrwx+ 1 guest guest 4722 Mar 22 2020 Photos
drwxr-xr-x 1 root root 0 May 20 10:54 .purge
drwxr-xr-x 1 root root 78 May 20 10:56 ._share
d?????????? ? ? ? ? ? .timemachine
drwxrwxrwx+ 1 guest guest 88 Oct 3 20:01 Transmission
drwxr-xr-x 1 root root 0 Feb 29 2020 .vault
drwxrwxrwx+ 1 guest guest 66 Oct 3 20:01 Videos
-rw-r--r-- 1 admin admin 1128 Oct 10 21:47 .volume_schedule.conf
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Sorry, it came out poorly, attached a screenshot
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Thanks, the screenshot is much easier.
Something looks really wrong - the system isn't able to read the metadata for the .timemachine subvolume. So the file system has somehow gotten corrupted. Not a good sign.
If you don't have a current backup, you should make one before proceeding. Then I suggest trying a btrfs scrub (which you can do from the volume settings wheel). I don't think it's that likely to help, but it is worth a try. If it fails, I think a factory reset/restore data from backup is the next step.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Ouch - I tried volume scrub, twice, in vain. The file system was indeed corrupted and you helped me (many thanks!) restore it via ssh as follows:
btrfs device scan
btrfs fi show
btrfs-zero-log /dev/md127
mount -t btrfs -r ro,recovery /dev/md127 /data
The volume did come back save for the timemachine data and access. The volume is quite big, and backing it up would be a major challenge not to mention cost. Is there anything else you think I could try to restore or wipe clean the timemachine functionality?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
@vasyam wrote:
Ouch - I tried volume scrub, twice, in vain. The file system was indeed corrupted and you helped me (many thanks!) restore it via ssh as follows:
btrfs device scan
btrfs fi show
btrfs-zero-log /dev/md127
mount -t btrfs -r ro,recovery /dev/md127 /data
The volume did come back save for the timemachine data and access. The volume is quite big, and backing it up would be a major challenge not to mention cost. Is there anything else you think I could try to restore or wipe clean the timemachine functionality?
It looks like the recovery didn't fully repair the volume. There is a btrfs check function you could try, but the btrfs community says it is high risk/last resort. You could also engage Netgear paid support: https://kb.netgear.com/69/ReadyNAS-Data-Recovery-Diagnostics-Scope-of-Service
As far as costs go, data recovery software and services have similar (or even more expensive) costs than backup, and of course data recovery often fails. Over the long run, you really should have a backup plan in place - otherwise, at some point you will lose all your data.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
There is a btrfs check function you could try, but the btrfs community says it is high risk/last resort.
Do you happen to have a link to that check function?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
@vasyam wrote:
Do you happen to have a link to that check function?
It's referenced here: https://btrfs.wiki.kernel.org/index.php/Btrfsck And of course it has it's own help page. https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-check
Note the warning: Warning: Do not use --repair unless you are advised to do so by a developer or an experienced user I've never used this function, and it could well do more damage. At the moment, timemachine is the only thing that appears to be broken. You could lose a lot more.
The process would be similar to what you did before:
btrfs device scan btrfs fi show btrfs check --repair /dev/md127
Though it would be more conservative to run btrfs check w/o the --repair option first, and see what it tells you. If it is limited to .timemachine, then I think the risk would be lower.
After the repair attempt, you can either reboot the NAS (and hope), or try mounting the volume manually first (and hope):
mount -t btrfs /dev/md127 /data
would mount it (not read-only), or you try the earlier mount command to mount it read-only without the recovery option.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Here is what I am getting - was not sure whether I should use --force before checking in with you)
root@NASHNAS:~# btrfs device scan
Scanning for Btrfs filesystems
root@NASHNAS:~# btrfs fi show
Label: '33ea29df:root' uuid: d2075c37-8181-4962-a9be-05ed860b1cf5
Total devices 1 FS bytes used 1.03GiB
devid 1 size 4.00GiB used 2.45GiB path /dev/md0
Label: '33ea29df:data' uuid: b7e1c21c-c4e7-4610-b04d-6681ebcea469
Total devices 1 FS bytes used 6.07TiB
devid 1 size 9.07TiB used 7.00TiB path /dev/md127
root@NASHNAS:~# btrfs check /dev/md127
ERROR: /dev/md127 is currently mounted, use --force if you really intend to check the filesystem
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
You should be doing this in tech support mode (when the volume wouldn't be mounted). Running it on a mounted volume increases the risk.
If I were in your position, I'd wait until I had a backup plan in place, and live w/o the timemachine backups for now.
That said, you'd boot into tech support mode using the boot menu. Then you log in with telnet instead of ssh. Username is root, the password is infr8ntdebug
After you gain access, you'd type
rnutil chroot btrfs device scan btrfs fi show
Then you can try the btrfs check command
start with this first
btrfs check /dev/md127
and if it looks like it only finds issues with .timemachine you can run it again with the --repair.
- 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: Deleting Redundant Time Machine Backup v2
@StephenB wrote:You should be doing this in tech support mode (when the volume wouldn't be mounted). Running it on a mounted volume increases the risk.
If I were in your position, I'd wait until I had a backup plan in place, and live w/o the timemachine backups for now.
That said, you'd boot into tech support mode using the boot menu. Then you log in with telnet instead of ssh. Username is root, the password is infr8ntdebug
After you gain access, you'd type
rnutil chroot btrfs device scan btrfs fi showThen you can try the btrfs check command
start with this first
btrfs check /dev/md127and if it looks like it only finds issues with .timemachine you can run it again with the --repair.
For some reason I am unable to telnet into the NAS booted in the tech mode. I read conflicting reports that telnet was no longer included with the Catalina MacOS although this option can be found in the service launch menu in the Terminal (as in the attached screenshot) according to others, and I did find it there. I am stuck a bit, trying to figure our what I am doing incorrectly
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
@StephenB wrote:You should be doing this in tech support mode (when the volume wouldn't be mounted). Running it on a mounted volume increases the risk.
If I were in your position, I'd wait until I had a backup plan in place, and live w/o the timemachine backups for now.
That said, you'd boot into tech support mode using the boot menu. Then you log in with telnet instead of ssh. Username is root, the password is infr8ntdebug
After you gain access, you'd type
rnutil chroot btrfs device scan btrfs fi showThen you can try the btrfs check command
start with this first
btrfs check /dev/md127and if it looks like it only finds issues with .timemachine you can run it again with the --repair.
There are errors, but I am not sure what they pertain too (I have attached a screenshot in case you have a second to take a look)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
@vasyam wrote:There are errors, but I am not sure what they pertain too (I have attached a screenshot in case you have a second to take a look)
There aren't that many, and the inodes are sequential - which is a good thing. It is possible to map the inode numbers to btrfs paths, but you'd need to mount the volume to do that.
In your case, the relevant commands would be
mount /dev/md127 /data btrfs inspect-internal inode-resolve 29475 /data btrfs inspect-internal inode-resolve 29476 /data btrfs inspect-internal inode-resolve 29477 /data btrfs inspect-internal inode-resolve 29478 /data btrfs inspect-internal inode-resolve 29479 /data btrfs inspect-internal inode-resolve 29480 /data btrfs inspect-internal inode-resolve 29481 /data umount /data
I don't know what it will report, given the errors, but the commands usually return a file or folder name.
Not sure what the --repair would do, but you should assume that those folders/files would be deleted.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
I am getting that there is no such file or directory
root@1YA293RR00327:/# mount /dev/md127 /data
root@1YA293RR00327:/# btrfs inspect-internal inode-resolve 29475 /data
ERROR: ino paths ioctl: No such file or directory
root@1YA293RR00327:/# btrfs inspect-internal inode-resolve 29476 /data
ERROR: ino paths ioctl: No such file or directory
root@1YA293RR00327:/# btrfs inspect-internal inode-resolve 29477 /data
ERROR: ino paths ioctl: No such file or directory
root@1YA293RR00327:/# btrfs inspect-internal inode-resolve 29478 /data
ERROR: ino paths ioctl: No such file or directory
root@1YA293RR00327:/# btrfs inspect-internal inode-resolve 29479 /data
ERROR: ino paths ioctl: No such file or directory
root@1YA293RR00327:/# btrfs inspect-internal inode-resolve 29480 /data
ERROR: ino paths ioctl: No such file or directory
root@1YA293RR00327:/# btrfs inspect-internal inode-resolve 29481 /data
ERROR: ino paths ioctl: No such file or directory
root@1YA293RR00327:/# umount /data
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Deleting Redundant Time Machine Backup v2
Should I try --repair you think? I do have backup of critical data, but would still hate to lose ~6Tb of media files