Re: [PLUG] fsck: recommended options?
On Sun, 4 Aug 2019, Rodney W. Grimes wrote: fsck -p is the proper normal invocation of fsck, and only if absolutely necessary should a fsck -y be run, and only as a very last resort. Rodney, Valid point. Thank you. No indication that fsck barfed on its way through the backup drive. Regards, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options?
> On Sun, 4 Aug 2019, wes wrote: > > > fsck does pretty well without parameters. If you wish to dispense with the > > need to authorize any repairs it suggests, having it just perform them, > > you can supply -p and/or -y. > > wes, > > Thank you. That was my recollection but it's been a very long time so > checking with those having more expertise is worth while. I can not stress enough how dangerious fsck -y is, that says blindly assume the answer is always yes, even if data loss is about to occur on a grand scale. fsck -p is the proper normal invocation of fsck, and only if absolutely necessary should a fsck -y be run, and only as a very last resort. fsck /dev/path if a fsck -p fails to clean the device is an interactive command, that one should undestand the questions and answer to before procedding to repair a file system. > Best regards, > Rich -- Rod Grimes rgri...@freebsd.org ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options?
On Sun, 4 Aug 2019, wes wrote: My best guess is that it's simple luck: on the occasion(s) you wanted to access the drive manually, it happened to be identified as sdb. Today, it happens to have been assigned sdc. This inability to predict which device name will be assigned to a given device is the reason the switch to the UUID method was done. Wes, Okay. While I've not seen this when manually mounting the backup drive I've seen different USB flash drives identified by the kernel with different device names, each consistently assigned the same name. Thanks very much, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options?
On Sun, Aug 4, 2019 at 11:13 AM Rich Shepard wrote: > On Sun, 4 Aug 2019, wes wrote: > > > fsck does pretty well without parameters. If you wish to dispense with > the > > need to authorize any repairs it suggests, having it just perform them, > you > > can supply -p and/or -y. > > Wes/Cathy: > > At first, fsck did not work when I specified the device as /dev/sdb which > is > how I access it when I need to restore a specific file. In /etc/fstab > that's > how it's listed: > /dev/sdb /mnt/hd ext3noauto,users,rw 0 0 > > Looking at the output of fdisk -l found no /dev/sdb, but a /dev/sdc which > is > not specifically in /etc/fstab. What is shown in that file is: > > UUID=da596a77-2fb4-41ed-881c-a3f8bb0ab437 /mnt/backup auto defaults 0 0 > > and fsck is working its way through the 500G on that drive. > > I'd like to understand how, when I turn on the drive after logging off so > cron can run dirvish each night, it's mounted on /mnt/backup as /dev/sdc > through the UUID designation, but when I want to access it manually I can > mount /dev/sdb on /dev/hd. > > TIA, > > Insufficient data for a meaningful answer. My best guess is that it's simple luck: on the occasion(s) you wanted to access the drive manually, it happened to be identified as sdb. Today, it happens to have been assigned sdc. This inability to predict which device name will be assigned to a given device is the reason the switch to the UUID method was done. -wes ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options?
On Sun, 4 Aug 2019, wes wrote: fsck does pretty well without parameters. If you wish to dispense with the need to authorize any repairs it suggests, having it just perform them, you can supply -p and/or -y. Wes/Cathy: At first, fsck did not work when I specified the device as /dev/sdb which is how I access it when I need to restore a specific file. In /etc/fstab that's how it's listed: /dev/sdb /mnt/hd ext3noauto,users,rw 0 0 Looking at the output of fdisk -l found no /dev/sdb, but a /dev/sdc which is not specifically in /etc/fstab. What is shown in that file is: UUID=da596a77-2fb4-41ed-881c-a3f8bb0ab437 /mnt/backup auto defaults 0 0 and fsck is working its way through the 500G on that drive. I'd like to understand how, when I turn on the drive after logging off so cron can run dirvish each night, it's mounted on /mnt/backup as /dev/sdc through the UUID designation, but when I want to access it manually I can mount /dev/sdb on /dev/hd. TIA, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options?
On Sun, 4 Aug 2019, Smith, Cathy wrote: I've just always used fsck -y Cathy, Then that's good enough for me, too. Best regards, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options?
I've just always used fsck -y -- Cathy L. Smith IT Engineer Pacific Northwest National Laboratory Operated by Battelle for the U.S. Department of Energy Phone: 509.375.2687 Fax: 509.375.4399 Email: cathy.sm...@pnnl.gov -Original Message- From: plug-boun...@pdxlinux.org On Behalf Of Rich Shepard Sent: Sunday, August 4, 2019 8:03 AM To: plug@pdxlinux.org Subject: [PLUG] fsck: recommended options? My daily logwatch report shows kernel errors on the external backup drive, /dev/sdb/, an ext3 file system. It's been a very long time since I had occasion to manually run fsck. After turning no the enclosure (and leaving the drive unmounted) what command line options should I add to fsck.ext3? TIA, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options?
On Sun, Aug 4, 2019 at 8:06 AM Rich Shepard wrote: > My daily logwatch report shows kernel errors on the external backup drive, > /dev/sdb/, an ext3 file system. It's been a very long time since I had > occasion to manually run fsck. > > After turning no the enclosure (and leaving the drive unmounted) what > command line options should I add to fsck.ext3? > > > fsck does pretty well without parameters. If you wish to dispense with the need to authorize any repairs it suggests, having it just perform them, you can supply -p and/or -y. -wes ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
[PLUG] fsck: recommended options?
My daily logwatch report shows kernel errors on the external backup drive, /dev/sdb/, an ext3 file system. It's been a very long time since I had occasion to manually run fsck. After turning no the enclosure (and leaving the drive unmounted) what command line options should I add to fsck.ext3? TIA, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
