Re: f10: fs errors; journal write error in flush_commit_list
Dario Nievas wrote: See if you can enable smartd to get further details it is running and no reports. -Check for hdparm parameters on your F10. Maybe there's some value that's not getting along with the sdb disk. i had not thought about hdparm. will log off internet and go have a look. thanks. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f10: fs errors; journal write error in flush_commit_list
Dario Nievas wrote: -Check for hdparm parameters on your F10. Maybe there's some value that's not getting along with the sdb disk. If possible, compare those values agains the other distros installed, looking for differences, Try to go with the bare minimun default values (yeah, the slow ones) and see if you prevent write errors with those ok, i checked for /etc/sysconfig/hdparm and they are bare minimum. so bare and minimum that there is no file in all 3 installs. :) open for suggestions on just what i should try in file. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
f10: fs errors; journal write error in flush_commit_list
greetings, from start of installation of f10, 4 months ago, to present, f10 has been having a problem of staying operational, in that after being up for a short time, it would bomb and have just now found problem. last update update was last night and while at command line, system showed error messages of what is happening. these are not all of messages, but should be enough for finding problem. previously; +++ REISERFS: abort (device sdb8): Journal write error in flush_commit_list REISERFS: Aborting journal for filesystem on sdb8. ext3_abort called. EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only +++ last night; +++ EXT3-fs error (device sdb6): in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device sdb6): in ext3_reserve_dirty_inode: Journal has aborted ext3_abort called. EXT3-fs error (device sdb6): in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only +++ google search shows hits on patches to previous kernels and other non relate info, but none of help. suggestions? pointers? links? tia. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f10: fs errors; journal write error in flush_commit_list
g wrote: greetings, from start of installation of f10, 4 months ago, to present, f10 has been having a problem of staying operational, in that after being up for a short time, it would bomb and have just now found problem. last update update was last night and while at command line, system showed error messages of what is happening. these are not all of messages, but should be enough for finding problem. previously; +++ REISERFS: abort (device sdb8): Journal write error in flush_commit_list REISERFS: Aborting journal for filesystem on sdb8. ext3_abort called. EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only Was there anything else logged? Reiserfs is reporting a write error while writing to the journal. Was a similar message logged by ext3 prior to the ext3_abort called message? Do you have any SCSI/SATA messages logged? This looks like you may have problems with your storage but these messages aren't sufficient to tell what's going on. Regards, Bryn. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f10: fs errors; journal write error in flush_commit_list
g wrote: greetings, from start of installation of f10, 4 months ago, to present, f10 has been having a problem of staying operational, in that after being up for a short time, it would bomb and have just now found problem. last update update was last night and while at command line, system showed error messages of what is happening. these are not all of messages, but should be enough for finding problem. previously; +++ REISERFS: abort (device sdb8): Journal write error in flush_commit_list REISERFS: Aborting journal for filesystem on sdb8. ext3_abort called. EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only +++ last night; +++ EXT3-fs error (device sdb6): in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device sdb6): in ext3_reserve_dirty_inode: Journal has aborted ext3_abort called. EXT3-fs error (device sdb6): in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only +++ google search shows hits on patches to previous kernels and other non relate info, but none of help. suggestions? pointers? links? tia. Dumb question - how much room is left on the drive? It is probably not the problem, but I like to check the simple things first. I would also check for I/O errors on the drive. Are there indications of drive going bad, power supply problems, etc? Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f10: fs errors; journal write error in flush_commit_list
On Wed, Jan 28, 2009 at 7:14 AM, g gel...@bellsouth.net wrote: greetings, from start of installation of f10, 4 months ago, to present, f10 has been having a problem of staying operational, in that after being up for a short time, it would bomb and have just now found problem. last update update was last night and while at command line, system showed error messages of what is happening. these are not all of messages, but should be enough for finding problem. previously; +++ REISERFS: abort (device sdb8): Journal write error in flush_commit_list REISERFS: Aborting journal for filesystem on sdb8. ext3_abort called. EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only +++ last night; +++ EXT3-fs error (device sdb6): in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device sdb6): in ext3_reserve_dirty_inode: Journal has aborted ext3_abort called. EXT3-fs error (device sdb6): in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only +++ google search shows hits on patches to previous kernels and other non relate info, but none of help. suggestions? pointers? links? How about running fsck on the drives? badblocks? ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f10: fs errors; journal write error in flush_commit_list
Bryn M. Reeves wrote: Was there anything else logged? logs are blank. this is shown in terminal view. Reiserfs is reporting a write error while writing to the journal. in first of listing to screen, reiserfs was first of screen writes, followed by ext3. Was a similar message logged by ext3 prior to the ext3_abort called message? screen messages are in order as i listed them. not complete, but in order. Do you have any SCSI/SATA messages logged? no scsi/sata error messages logged. there may be something, but it is not anything related to errors. This looks like you may have problems with your storage but these messages aren't sufficient to tell what's going on. my apologies for lack of details in post. i was too disappointed in lack of finding anything from google search and not thinking fully when i posted. ~~~ in this box, i also have scientific linux 5.4 and fedora 8, both with latest updates, and do not have any problems with hard drives. /dev/sda1 / sl5.4 ext3 journal /dev/sda2 swap /dev/sda5 /home sl5.4 reiserfs journal /dev/sdb1 /bootreiserfs /dev/sdb2 swap /dev/sdb5 / f8 ext3 journal /dev/sdb6 / f10ext3 journal /dev/sdb7 [spare] reiserfs journal /dev/sdb8 /usr f10reiserfs journal /dev/sdb9 /var f10reiserfs journal /dev/sdb10 [spare] reiserfs journal /dev/sdb11 /homereiserfs journal /dev/sdb12 / f8 ext3 journal /dev/sda is used for internet only, with sdb unmounted /dev/sdb is used for non internet, with sda mounted under /hd/a/01,05 /dev/sda1 has a /boot directory and files for sl 5.4 only /dev/sdb1 has boot files for all distributions ~~~ problem was present before mounting additional partitions under f10, and before moving f10 /usr and /var to reiserfs, which was done for more room to run updates. in first post, i stated; from start of installation of f10, 4 months ago, to present, f10 has been having a problem of staying operational, in that after being up for a short time, it would bomb and have just now found problem. to clarify, i had seen problem previously, but dismissed it and continued with trying to learn f10 and kde4. i always boot level 3 with initial login as user at vt-f1, and start kde from vt-f5. when i first noticed that there was a problem, i had kde running and went to vt-f3 to run first updates because i was having problems with packagekit. update failed, and i dismissed it as a kde problem. after reboot, i logged in as root and ran 'yum update' without problems. rebooted and went to f8 to do work until i had f10 ready to move operations to f10. i have made several more updates which succeeded, and rebooted after, returning to sl5.4 and f8. now, any time that i stay in f10/kde, i get lockup after 15 to 20 minutes. again, thanks for help. any further advice will be greatly appreciated as i would like to remove f8 to make room for f12. [ i like even numbers. :) ] later -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f10: fs errors; journal write error in flush_commit_list
Mikkel L. Ellertson wrote: Dumb question - how much room is left on the drive? It is probably not the problem, but I like to check the simple things first. there are no dumb questions. only dumb mistakes from not asking questions. over 1g0 byte. i had problem before moving /usr and /var to additional partitions to have room for running updates. [see reply to reeves] I would also check for I/O errors on the drive. Are there indications of drive going bad, power supply problems, etc? drives and ps ok. i do run hd checks to ensure all ok. thanks for your reply. open to more questions/suggestions. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f10: fs errors; journal write error in flush_commit_list
Aldo Foot wrote: How about running fsck on the drives? badblocks? standard practice is to run manual fsck.ext3 and reiserfsck after any manual restart. no bad blocks. thanks for reply. still open for suggestions. later. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f10: fs errors; journal write error in flush_commit_list
I usually see those errors at work when there are hardware problems (disks dying, or temporary SAN issues). What I would do is: -Check for hardware problems on sdb (but you say you have other distros installed without problems, so that makes it tricky). See if you can enable smartd to get further details from the storage hardware -Check for hdparm parameters on your F10. Maybe there's some value that's not getting along with the sdb disk. If possible, compare those values agains the other distros installed, looking for differences, Try to go with the bare minimun default values (yeah, the slow ones) and see if you prevent write errors with those Hope that helps, at least a bit later On Wed, Jan 28, 2009 at 7:39 PM, g gel...@bellsouth.net wrote: Aldo Foot wrote: How about running fsck on the drives? badblocks? standard practice is to run manual fsck.ext3 and reiserfsck after any manual restart. no bad blocks. thanks for reply. still open for suggestions. later. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
