![]() | |||||||||||||
Messages in this thread |
On Wed, Nov 28, 2001 at 11:12:22PM -0500, Alexander Viro wrote: > > This was on a reiserfs system, btw. > > Obvious tests: > a) 2.5.1-pre2 2.5.1-pre2 was fine. > b) 2.5.1-pre2 + fs/super.c from 2.5.1-pre3 > c) 2.5.1-pre3 + fs/super.c from 2.5.1-pre2 > (fs/super.c changes are independent from everything else). I'll try option c and let you know what happens. > Another possibility is silent fs corruption from 2.5.0/2.4.15 - if you > ran these kernels you really ought to do fsck -f (or whatever is used > to force recovery of reiserfs). I did have some nasty errors while running dbench around those kernel versions. To be safe, I did a cpio backup and re-mkreiserfs'd three filesystems with 2.4.16. The filesystem that fsync02 hung on was one of the recently rebuilt filesystems. -- Randy Hron - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:13 [W:0.300 / U:0.040 seconds] ©2003-2008 Jasper Spaans | |||||||||||||