linux-ext4 - [Bug 34302] Errors from kjournald

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 May 2011 16:27:27 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 34302] Errors from kjournald

https://bugzilla.kernel.org/show_bug.cgi?id=34302





--- Comment #2 from Tom Moore <tmoore@...tial.ca>  2011-05-03 16:27:25 ---
Yes, it appears that there is additional in the syslog that is not in the
messages file (sorry about that).

May  3 01:02:25 fawkes kernel: [307200.700498] INFO: task kjournald:6416
blocked for more than 120 seconds.
May  3 01:02:25 fawkes kernel: [307200.700506] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

The machine was doing a full backup of about 1Tb of data at the time using
backuppc, so that might be the reason that the journal could not keep up.  It
is possible that something else in the crontab also kicked off at around that
time.  I am a bit confused by the messages however.  The backup source is 2
SATA 3 (6Gbs) disks in a Raid-1 config; the backup target is 1 SATA2 (3gbs)
disk.  The final message of concern was 

May  3 01:40:09 fawkes kernel: [309464.781078] ata8.00: exception Emask 0x0
SAct 0x2 SErr 0x0 action 0x6 frozen
May  3 01:40:09 fawkes kernel: [309464.781091] ata8.00: failed command: READ
FPDMA QUEUED
May  3 01:40:09 fawkes kernel: [309464.781107] ata8.00: cmd
60/08:08:47:0a:ab/00:00:45:00:00/40 tag 1 ncq 4096 in
May  3 01:40:09 fawkes kernel: [309464.781111]          res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May  3 01:40:09 fawkes kernel: [309464.781118] ata8.00: status: { DRDY }
May  3 01:40:09 fawkes kernel: [309464.781131] ata8: hard resetting link
May  3 01:40:10 fawkes kernel: [309465.112103] ata8: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May  3 01:40:10 fawkes kernel: [309465.119531] ata8.00: configured for UDMA/133
May  3 01:40:10 fawkes kernel: [309465.119543] ata8.00: device reported invalid
CHS sector 0
May  3 01:40:10 fawkes kernel: [309465.119559] ata8: EH complete

I am not 100% sure which disk ata8 corresponds to.  I tried looking through the
boot log to figure out the device assignments, but it was a bit confusing, It
appears that ata8.00 is one of the source raid disks.  If so, I wonder why it
got reset?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html