public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: ralfconn <mentadent47@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] backup horror story (happy ending)
Date: Sat, 9 Nov 2024 11:30:28 +0100	[thread overview]
Message-ID: <713323a1-bd58-4607-898f-db2aedc9942c@yahoo.com> (raw)
In-Reply-To: 713323a1-bd58-4607-898f-db2aedc9942c.ref@yahoo.com

I have a 4Tb hard disk half full of videos and photos my daughter took 
with her cell phone over the years, shared with Win11 in a dual boot box 
so it is NTFS-formatted. The disk is backed up on a different EXT4 disk 
and the backup is performed by (ana)cron via an rsync bash script.

Last evening there was a power outage. When I rebooted in linux the NTFS 
disk would not mount. OK, just e2fsck the disk and it will fix it, I 
thought, forgetting that it was an NTFS not EXT. e2fsck -y starts 
finding and fixing hundreds of issues on the disk, till I get bored, I 
stop it and reboot into Win11, which chkdsk's it and mounts with no 
problem in less than 10s.

Finally I realize the huge mistake I had made, allowing e2fsck to delete 
thousands of otherwise fine clusters/nodes/whatever on a filesystem it 
does not understand.

But I have a backup, no problem... till I realize the cron job had 
already run so it had overwritten the old files with the new, corrupt 
versions.

Fortunately rsync uses the file access date to quickly find potential 
differences and since the e2fsck did not touch those the backup was 
still fine.

Later I found that the disk did not mount in linux due to mount not 
finding anymore the NTFS's UUID that I had in fstab, but it did mount 
fine with /dev/sdx.

I felt like a triple-idiot.

raf




       reply	other threads:[~2024-11-09 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <713323a1-bd58-4607-898f-db2aedc9942c.ref@yahoo.com>
2024-11-09 10:30 ` ralfconn [this message]
2024-11-09 14:43   ` [gentoo-user] backup horror story (happy ending) Rich Freeman
2024-11-09 21:01   ` Philip Webb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=713323a1-bd58-4607-898f-db2aedc9942c@yahoo.com \
    --to=mentadent47@yahoo.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox