WU's fail after 100%, left over work files, ext4 cause?

Moderators: Site Moderators, PandeGroup

Re: WU's fail after 100%, left over work files, ext4 cause?

Postby chrisretusn » Sat Feb 13, 2010 4:11 am

Out of curiosity, why are your folding off a live CD via ram disk? At least that is what it looks like to me.
Image
Folding on Slackware Linux.
chrisretusn
 
Posts: 196
Joined: Sat Feb 02, 2008 10:12 am
Location: Philippines

Re: WU's fail after 100%, left over work files, ext4 cause?

Postby bruce » Tue Mar 16, 2010 12:12 am

Ext4 is not the only issue here. Other filesystems and other OSs have similar features.

We're seeing an number of reports where checkpoints cannot be recovered after a sysem crash. It's very difficult to tell whether this is related to delayed allocation or delayed writes or neither. Certainly there is a tradeoff between file system speed and reliability. Consider the following
http://es.linuxfoundation.org/news-medi ... le-problem

If you or your system designer want to speed up your filesystem, there's no doubt that these techniques work, provided you don't really care what happens if the system crashes or you have to do a forced reboot when the file system is still dirty. If you think that FAH spends too much time waiting for the fsync() processes to finish, consider the alternatives.
bruce
 
Posts: 22721
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: WU's fail after 100%, left over work files, ext4 cause?

Postby chrisretusn » Tue Mar 16, 2010 12:30 am

Agree. I spent considerable time testing this and results were mixed with ext4. While I could reproduce failures most of the time it was not 100% of the time. One thing for sure, since switching back to the jfs file system I have not had any more problems.
chrisretusn
 
Posts: 196
Joined: Sat Feb 02, 2008 10:12 am
Location: Philippines

Re: WU's fail after 100%, left over work files, ext4 cause?

Postby Wrish » Tue Mar 16, 2010 1:40 am

Wow, I didn't realize the HFS+ system in OS X was merely exhibiting the delayed write behavior found in -ext4. That would explain why most people never see this issue - the ones running Windows with NTFS or Linux with -ext3, both with default settings.
Wrish
 
Posts: 319
Joined: Thu Jan 28, 2010 5:09 am

Previous

Return to Linux CPU V6 Client

Who is online

Users browsing this forum: No registered users and 1 guest

cron