[opensuse-kernel] Filesystem becomes readonly when listening to music
Hi, If I listen to music for some time (I guess around 1 hour after starting listening to music) my filesystem becomes readonly and I can't continue using the system, so I have to reboot. When I do it, fsck has to check the filesystem for 20 minutes and find some errors but I have never lost data (yet). I have already run the hard drive auto-diagnostic in the notebook BIOS (HP Pavillion dv2872br) but no problems were found. At first I thought the problem was with the nvidia driver, but at the nvidia forum they said there was nothing related to nvidia in my log files and I had no video problems. Anyway, as the filesystem gets readonly, no information is recorded to the log files. I could get a lot of information running nvidia-bug-report.sh in a folder in my windows partition (witch was not readonly), it's output is attached to this message. A relevant part of the log is: EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device dm-0) in ext3_dirty_inode: Journal has aborted ext3_abort called. EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only JBD: Detected IO errors while flushing file data on dm-0 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Thanks, Danilo Luvizotto
Hi, On Tue 07-04-09 12:52:05, Danilo Luvizotto wrote:
If I listen to music for some time (I guess around 1 hour after starting listening to music) my filesystem becomes readonly and I can't continue using the system, so I have to reboot. When I do it, fsck has to check the filesystem for 20 minutes and find some errors but I have never lost data (yet). I have already run the hard drive auto-diagnostic in the notebook BIOS (HP Pavillion dv2872br) but no problems were found. At first I thought the problem was with the nvidia driver, but at the nvidia forum they said there was nothing related to nvidia in my log files and I had no video problems. Anyway, as the filesystem gets readonly, no information is recorded to the log files. I could get a lot of information running nvidia-bug-report.sh in a folder in my windows partition (witch was not readonly), it's output is attached to this message. A relevant part of the log is:
EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device dm-0) in ext3_dirty_inode: Journal has aborted ext3_abort called. EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only JBD: Detected IO errors while flushing file data on dm-0 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) This is a known bug. Should be fixed by the nearest kernel update (which is already in QA AFAIK). Thanks for the report.
Honza
--
Jan Kara
participants (2)
-
Danilo Luvizotto -
Jan Kara