On 3/2/25 14:35, David Christensen wrote:
At this point, I am uncertain if the /home ext4 file systems are correct on either the OS disc or the copied image disc (?).
I did a "fsck -f" on each filesystem. Many had no errors, most of the rest were just "this inode is too wide". So they're all correct _now_, and I'll back up again next weekend.
The "norecovery" option for mount(8) seems like a dangerous design choice. "readonly" is supposed to mean "do not write to disk".
Yeah, that's what I thought too.
I must remember that land mine if and when I want to do forensic work.
> eben@cerberus:/$ sudo smartctl -a /dev/sda > smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-31-amd64] (local build) > Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org > > === START OF INFORMATION SECTION === > Model Family: Seagate BarraCuda 3.5 (SMR) > Device Model: ST2000DM008-2UB102 AIUI SMR does not work well for OS (e.g. /tmp, swap) and general-purpose (e.g. /home) disks that see frequent small random write workloads. I prefer small high-quality 2.5" SSD's (Intel SSD 520 Series 60 GB) for my OS and /home disks, and put my bulk data on a file server. I would re- purpose that HDD for images -- CMR should be okay for large sequential write workloads.
?MR=Shielded / Conventional Magnetic Recording? How do I tell a priori which drives are SMR and which are CMR?
> SMART Self-test log structure revision number 1 > No self-tests have been logged. [To run self-tests, use: smartctl -t] Are you running tests periodically?
I haven't been, but perhaps I should add that to my after-backup routine.
