f10: fs errors; journal write error in flush_commit_list

[Dario Nievas]

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 <geleem at 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 at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>