Re: [PLUG] fsck: recommended options? [UPDATE]
True. What I was hoping to suggest is, that the messages from the ext4 diver, are labeled as ext4, not necessarily ext3; regardless of the filesystem being operated on. Of course, that has little to address his fschk errors and USB mount point confusion. I will not speculate on that part. -T ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
On Mon, Aug 5, 2019 at 7:24 PM Tomas Kuchta wrote: > I presume that this is the patch removing ext3 kernel driver. > > https://lkml.org/lkml/2015/7/15/438 > > -T > > Rich was concerned about the origins of a logwatch message for one of his filesystems, which makes sense, his drives are using an old filesystem, so it sends him a friendly warning. The removal of the driver is only relevant in the sense that it makes such warnings a guarantee. The driver is gone, but EXT3 is still actively being used. So on modern systems you see a benine message pointing to a potential point of failure. > On Mon, Aug 5, 2019, 17:11 Tomas Kuchta > wrote: > > > You guys are running distro I am not familiar with, but I do not think > > that there is such a thing like ext3 kernel module/driver anymore for > > couple of years. > > > > I believe that the ext4 driver/module is used for both ext3 and ext4. So, > > you may be chasing ghost with focussing on 3/4 discrepancy. > > > > Warning: please verify my statement with your distro. > > > > Tomas > > > > On Mon, Aug 5, 2019, 13:12 Rich Shepard > wrote: > > > >> On Mon, 5 Aug 2019, Ben Koenig wrote: > >> > >> > However to answer your question of "why am I seeing this", note that > you > >> > are mounting EXT3 using the EXT4 drivers. > >> > >> Which is not the result of anything I've explicitly done. When the > system > >> started doing this I have no idea. > >> > >> Thanks, > >> > >> 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 > ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
I presume that this is the patch removing ext3 kernel driver. https://lkml.org/lkml/2015/7/15/438 -T On Mon, Aug 5, 2019, 17:11 Tomas Kuchta wrote: > You guys are running distro I am not familiar with, but I do not think > that there is such a thing like ext3 kernel module/driver anymore for > couple of years. > > I believe that the ext4 driver/module is used for both ext3 and ext4. So, > you may be chasing ghost with focussing on 3/4 discrepancy. > > Warning: please verify my statement with your distro. > > Tomas > > On Mon, Aug 5, 2019, 13:12 Rich Shepard wrote: > >> On Mon, 5 Aug 2019, Ben Koenig wrote: >> >> > However to answer your question of "why am I seeing this", note that you >> > are mounting EXT3 using the EXT4 drivers. >> >> Which is not the result of anything I've explicitly done. When the system >> started doing this I have no idea. >> >> Thanks, >> >> 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? [UPDATE]
You guys are running distro I am not familiar with, but I do not think that there is such a thing like ext3 kernel module/driver anymore for couple of years. I believe that the ext4 driver/module is used for both ext3 and ext4. So, you may be chasing ghost with focussing on 3/4 discrepancy. Warning: please verify my statement with your distro. Tomas On Mon, Aug 5, 2019, 13:12 Rich Shepard wrote: > On Mon, 5 Aug 2019, Ben Koenig wrote: > > > However to answer your question of "why am I seeing this", note that you > > are mounting EXT3 using the EXT4 drivers. > > Which is not the result of anything I've explicitly done. When the system > started doing this I have no idea. > > Thanks, > > 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? [UPDATE]
On Mon, 5 Aug 2019, Ben Koenig wrote: However to answer your question of "why am I seeing this", note that you are mounting EXT3 using the EXT4 drivers. Which is not the result of anything I've explicitly done. When the system started doing this I have no idea. Thanks, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
On Mon, 5 Aug 2019, Galen Seitz wrote: As Rodney says, I think this error is likely a one-off. With a removable drive, an error like this isn't particularly unusual. You may want to consider rebooting. This isn't necessarily related, but when using a scsi tape drive, I would occasionally get errors that were most easily cleared by rebooting. Galen, It's a warning, not an error. And I don't have any SCSI devices since I removed the tape drive. The system's been rebooted, too. BTW, I'm not seeing the error/warning in your grep of dmesg. I'd look in /var/log/messages (or the Slackware equivalent) to see if you can spot anything there. # grep WARNING /var/log/messages finds nothing. Thanks, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
It does look like an old message laying around. However to answer your question of "why am I seeing this", note that you are mounting EXT3 using the EXT4 drivers. While yes, this is possible, it will not be a totally clean process. Those warnings could be a result of the difference in features for ext 3 and 4. It's letting you know that things look funky and suggesting that you troubleshoot. You can mount 3 as 4, but not 4 as 3, if that makes any sense. As long as this is intentional, you are probably fine. My question is why is it using the EXT4 subsystem for your older drives? Shouldn't you be able to cleanly mount using the original EXT3 stack? On Mon, Aug 5, 2019 at 9:50 AM Galen Seitz wrote: > On 8/5/19 9:02 AM, Rich Shepard wrote: > > On Mon, 5 Aug 2019, Rodney W. Grimes wrote: > > > >> I further suspect the error from logwatch is an event in history that > has > >> long since been resolved and it just continues to report it as a recent > >> event. > > > > Rodney, > > > > I thought that was the case but not sufficiently knowledgeable to know > for > > sure. Also, the kernel issues a warning, not an error, so the > > criticality is > > lower. > > As Rodney says, I think this error is likely a one-off. With a > removable drive, an error like this isn't particularly unusual. You may > want to consider rebooting. This isn't necessarily related, but when > using a scsi tape drive, I would occasionally get errors that were most > easily cleared by rebooting. > > BTW, I'm not seeing the error/warning in your grep of dmesg. I'd look > in /var/log/messages (or the Slackware equivalent) to see if you can > spot anything there. > > galen > -- > Galen Seitz > gal...@seitzassoc.com > ___ > 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? [UPDATE]
On 8/5/19 9:02 AM, Rich Shepard wrote: On Mon, 5 Aug 2019, Rodney W. Grimes wrote: I further suspect the error from logwatch is an event in history that has long since been resolved and it just continues to report it as a recent event. Rodney, I thought that was the case but not sufficiently knowledgeable to know for sure. Also, the kernel issues a warning, not an error, so the criticality is lower. As Rodney says, I think this error is likely a one-off. With a removable drive, an error like this isn't particularly unusual. You may want to consider rebooting. This isn't necessarily related, but when using a scsi tape drive, I would occasionally get errors that were most easily cleared by rebooting. BTW, I'm not seeing the error/warning in your grep of dmesg. I'd look in /var/log/messages (or the Slackware equivalent) to see if you can spot anything there. galen -- Galen Seitz gal...@seitzassoc.com ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
On Mon, 5 Aug 2019, Rodney W. Grimes wrote: I further suspect the error from logwatch is an event in history that has long since been resolved and it just continues to report it as a recent event. Rodney, I thought that was the case but not sufficiently knowledgeable to know for sure. Also, the kernel issues a warning, not an error, so the criticality is lower. This many not be looking at exactly what you need, better: dmesg | grep 'sd[a-z]' # dmesg | grep sd[a-z] [4.299451] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [4.319311] sd 0:0:0:0: [sda] Write Protect is off [4.328956] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.328969] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.409795] sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 > [4.420117] sd 0:0:0:0: [sda] Attached SCSI disk [6.737025] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [6.747125] EXT4-fs (sda1): INFO: recovery required on readonly filesystem [6.756263] EXT4-fs (sda1): write access will be enabled during recovery [6.896368] EXT4-fs (sda1): recovery complete [6.928730] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 11.840042] Adding 15623208k swap on /dev/sda3. Priority:-1 extents:1 across:15623208k [ 12.553724] EXT4-fs (sda1): re-mounted. Opts: (null) [ 43.351603] EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem [ 43.376859] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 43.418966] EXT4-fs (sda5): mounting ext3 file system using the ext4 subsystem [ 43.464852] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) [ 43.483693] EXT4-fs (sda6): mounting ext3 file system using the ext4 subsystem [ 43.535564] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [ 43.573277] EXT4-fs (sda7): mounting ext3 file system using the ext4 subsystem [ 43.625133] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null) [ 43.639373] EXT4-fs (sda8): mounting ext3 file system using the ext4 subsystem [ 43.713759] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null) [ 43.755338] EXT4-fs (sda9): mounting ext3 file system using the ext4 subsystem [ 43.797319] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null) This with the external drive off (it's normal state during the day). Thanks, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
I highly suspect much of the confusion, both by the system, and us humans, is that these drives are external USB drives and they get assigned different drive designators at different times what was once /dev/sdb may next be /dev/sdc. I further suspect the error from logwatch is an event in history that has long since been resolved and it just continues to report it as a recent event. > So based on the info you've given, more information is required to > understand the problem. > > Basically: > - your logwatch messages says you have a problem with the EXT4 filesystem > on /dev/sdb. > - you say /dev/sdb is formatted as EXT3. > > That doesn't line up. There's no reason why you should be mounting an EXT3 > partition as EXT4 unless you have a specific reason to do so ( and I very > much doubt that you do). > > Since logwatch isn't giving you the error, check dmesg for sdb related > messages: > $ dmesg |grep sdb This many not be looking at exactly what you need, better: dmesg | grep 'sd[a-z]' > > The output of the above command might include the error that logwatch is > referring to. if you are unable to find the exact error in dmesg, reproduce > it using the following steps (as root) > $ umount /dev/sdb > $ dmesg > log-before.txt > $ mount /dev/sdb > $ dmesg > log-after.txt > $ diff log-before.txt log-after.txt > > The output of diff will give you only the messages that occured AFTER you > mounted /dev/sdb. Any errors, warnings, and messages that occur as part of > the mount process will be shown there, in all their gory detail. If there > is in fact a problem with this particular drive, you will see it in the > difference between the before and after logs. mount does not report errors to stdout?? > > > On Mon, Aug 5, 2019 at 7:39 AM Rich Shepard > wrote: > > > On Mon, 5 Aug 2019, Ben Koenig wrote: > > > > > Those kernel warnings say EXT4, but your fstab and fsck usage all say > > > ext3. > > > > > > Are you absolutely sure this volume > > > is ext3? Because the kernel has other ideas > > > > Yes. > > > > This host, and the external drive, were formatted as ext3. Only my 64-bit > > hosts are formatted ext4. > > > > 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 > -- Rod Grimes rgri...@freebsd.org ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
On Mon, 5 Aug 2019, Ben Koenig wrote: Basically: - your logwatch messages says you have a problem with the EXT4 filesystem on /dev/sdb. - you say /dev/sdb is formatted as EXT3. Ben, That's why I'm trying to understand why logwatch started showing this warning last week. There is no /dev/sdb until I insert a USB flash drive or turn on the external backup hard drive and manually mount it. When I turn on the external hard drive fdisk -l shows /dev/sda and /dev/sdc, the external drive is the latter. By default, the external drive's UUID is mounted on /dev/backup where dirvish finds it each night. Since logwatch isn't giving you the error, check dmesg for sdb related messages: $ dmesg |grep sdb Nothing. This desktop is acting very flaky which is why I'm trying to migrate to the new one. The kernel warning might well be part of the flakyness. Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
So based on the info you've given, more information is required to understand the problem. Basically: - your logwatch messages says you have a problem with the EXT4 filesystem on /dev/sdb. - you say /dev/sdb is formatted as EXT3. That doesn't line up. There's no reason why you should be mounting an EXT3 partition as EXT4 unless you have a specific reason to do so ( and I very much doubt that you do). Since logwatch isn't giving you the error, check dmesg for sdb related messages: $ dmesg |grep sdb The output of the above command might include the error that logwatch is referring to. if you are unable to find the exact error in dmesg, reproduce it using the following steps (as root) $ umount /dev/sdb $ dmesg > log-before.txt $ mount /dev/sdb $ dmesg > log-after.txt $ diff log-before.txt log-after.txt The output of diff will give you only the messages that occured AFTER you mounted /dev/sdb. Any errors, warnings, and messages that occur as part of the mount process will be shown there, in all their gory detail. If there is in fact a problem with this particular drive, you will see it in the difference between the before and after logs. On Mon, Aug 5, 2019 at 7:39 AM Rich Shepard wrote: > On Mon, 5 Aug 2019, Ben Koenig wrote: > > > Those kernel warnings say EXT4, but your fstab and fsck usage all say > > ext3. > > > > Are you absolutely sure this volume > > is ext3? Because the kernel has other ideas > > Yes. > > This host, and the external drive, were formatted as ext3. Only my 64-bit > hosts are formatted ext4. > > 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? [UPDATE]
On Mon, 5 Aug 2019, Ben Koenig wrote: Those kernel warnings say EXT4, but your fstab and fsck usage all say ext3. Are you absolutely sure this volume is ext3? Because the kernel has other ideas Yes. This host, and the external drive, were formatted as ext3. Only my 64-bit hosts are formatted ext4. Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] fsck: recommended options? [UPDATE]
Those kernel warnings say EXT4, but your fstab and fsck usage all say ext3.
Are you absolutely sure this volume
is ext3? Because the kernel has other ideas
On Mon, Aug 5, 2019, 6:01 AM Rich Shepard wrote:
> On Sun, 4 Aug 2019, 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.
>
> Yesterday, thanks to advice from Wes, Cathy, and Rodney I ran fsck on the
> external backup drive using it's UUID. This morning's logwatch report still
> contains the warnings:
>
> ### Logwatch 7.4.3 (04/27/16)
> Processing Initiated: Mon Aug 5 03:10:03 2019
> Date Range Processed: yesterday
>( 2019-Aug-04 )
>Period is day.
> Detail Level of Output: 0
> Type of Output/Format: mail / text
> Logfiles for Host: salmo
> ##
>
> - Kernel Begin
>
> WARNING: Kernel Errors Present
> EXT4-fs (sdb): error count since last ...: 1 Time(s)
> EXT4-fs (sdb): initial error at time 15645858 ...: 1 Time(s)
> EXT4-fs (sdb): last error at time 15645858 ...: 1 Time(s)
>
> -- Kernel End -
>
> The fstab entries for this drive are:
>
> UUID=da596a77-2fb4-41ed-881c-a3f8bb0ab437 /mnt/backup auto defaults 0 0
> /dev/sdb /mnt/hd ext3noauto,users,rw 0 0
>
> I want to understand the kernel warning and fix whatever causes it.
>
> The fsck man page says that -p is the same as the deprecated -a, especially
> for e2fsck. The fsck.ext3 man page says that -p "Automatically repair
> ("preen") the file system. This option will cause e2fsck to automatically
> fix any filesystem problems that can be safely fixed without human
> intervention."
>
> Should I run e2fsck -p on this drive?
>
> Insights wanted,
>
> 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? [UPDATE]
On Sun, 4 Aug 2019, 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.
Yesterday, thanks to advice from Wes, Cathy, and Rodney I ran fsck on the
external backup drive using it's UUID. This morning's logwatch report still
contains the warnings:
### Logwatch 7.4.3 (04/27/16)
Processing Initiated: Mon Aug 5 03:10:03 2019
Date Range Processed: yesterday
( 2019-Aug-04 )
Period is day.
Detail Level of Output: 0
Type of Output/Format: mail / text
Logfiles for Host: salmo
##
- Kernel Begin
WARNING: Kernel Errors Present
EXT4-fs (sdb): error count since last ...: 1 Time(s)
EXT4-fs (sdb): initial error at time 15645858 ...: 1 Time(s)
EXT4-fs (sdb): last error at time 15645858 ...: 1 Time(s)
-- Kernel End -
The fstab entries for this drive are:
UUID=da596a77-2fb4-41ed-881c-a3f8bb0ab437 /mnt/backup auto defaults 0 0
/dev/sdb /mnt/hd ext3noauto,users,rw 0 0
I want to understand the kernel warning and fix whatever causes it.
The fsck man page says that -p is the same as the deprecated -a, especially
for e2fsck. The fsck.ext3 man page says that -p "Automatically repair
("preen") the file system. This option will cause e2fsck to automatically
fix any filesystem problems that can be safely fixed without human
intervention."
Should I run e2fsck -p on this drive?
Insights wanted,
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
