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
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
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
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.
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
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
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
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
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,
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
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
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
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
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
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
15 matches
Mail list logo
