Date: 15 Apr 2023 22:13:47 -0400 From: "John R. Levine" <johnl@iecc.com> To: "Gary Aitken" <freebsd@dreamchaser.org>, freebsd-questions@freebsd.org Subject: Re: frequent disk error, need guidance Message-ID: <0baa336e-171d-081a-0f59-a2a165f4517d@iecc.com> In-Reply-To: <5793cdd5-c365-7769-49e9-366cb367a8a0@dreamchaser.org> References: <20230415204721.DD803BF2E2EA@ary.qy> <5793cdd5-c365-7769-49e9-366cb367a8a0@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I'd shut down to single user, make a /.snap directory, and do dump -L >> to tell it to make a snapshot before dumping. That should work OK. > > Thanks. > (Needed to mount /tmp read-write) > The -L didn't work because boot -s mounted the filesystem read-only; > at least that's what it claimed: > > dump -0 -L -f - /dev/ada0p2 | restore -r -Dv -f - > Verify tape and initialize maps > DUMP: WARNING: -L ignored for read-only filesystem > > Not sure I understand that; > does -s normally start in read-only mode? > Has it always done that? It's been quite a while since I did that. Don't remember, but if the filesystem is read-only, that's even better than -L because you know it won't change at all. > It looks like the bad blocks/sectors were files in > /var/db/freebsd-update/files/xxx.gz > I unzipped a file in that directory and it appears that they are the > saved files from the old system when upgrading. Is that correct? > Any reason not to remove all files in > /var/db/freebsd-update/files > since the upgraded to 12.x system has been running for several months > now? I think that should be OK too. Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0baa336e-171d-081a-0f59-a2a165f4517d>