Strange kern.log error log entries.

Lennart Sorensen lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Wed Jul 10 14:09:34 UTC 2013


On Wed, Jul 10, 2013 at 09:31:25AM -0400, Myles Braithwaite wrote:
> After yesterdays power outage a number of my computers are showing the
> following errors in the /var/log/kern.log:
> 
> $ cat /var/log/kern.log | grep sd | grep re-mounted
> Jul  8 23:59:46 hawkeye kernel: [    6.997538] EXT4-fs (sda1):
> re-mounted. Opts: errors=remount-ro
> Jul  9 01:51:56 hawkeye kernel: [    8.208955] EXT4-fs (sda1):
> re-mounted. Opts: errors=remount-ro
> Jul  9 10:15:43 hawkeye kernel: [    8.115715] EXT4-fs (sda1):
> re-mounted. Opts: errors=remount-ro
> 
> From what I can tell from Google this just means that the power went
> out and the computer did a hard reset.
> 
> Should I be worried that the drive is going to die?

Are you sure those aren't during boot when the fsck has completed and
the root FS is remounted from r/o to r/w?

I see this on this machine during boot:

[   58.525614] EXT4-fs (md0): re-mounted. Opts: (null)
[   58.817568] EXT4-fs (md0): re-mounted. Opts: errors=remount-ro

After all, 8 seconds after boot seems a lot like the time it would
remount the filesystem read/write after doing the boot time fsck.

As far as I can read that message, it says "I remounted the filesystem
with different options.  The current options are: errors=remount-ro".

And since I have fstab like this:
UUID=9e4f39b8-9661-4674-8f03-f458f487b671 / ext4 errors=remount-ro 0 1

That would in fact be the correct options to be using.  After all 'ro'
is a non default option, so it would probably boot mounted with 'ro',
then remount with options 'errors=remount-ro', but no longer 'ro',
meaning it is now read/write instead.

-- 
Len Sorensen
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list