Re: dump locks again [SOLVED]
Kris Kennaway ha scritto: Andrea Venturoli wrote: Kris Kennaway ha scritto: This was fixed in 7.0-STABLE. I confirm upgrading to 7.0-STABLE solved this. Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dump locks again
Hello. I googled around for this but found only very old threads (from 2005 or so). I'm taking dumps of a new box I build, which runs 7.0/amd64 on 8 cores with harware RAID-5 (ciss driver). This is an example of the command I issue: dump -0 -a -f usr.dump -L -h 0 -u /usr Almost always, the dump process will work up to Pass IV (regular files), but then stuck there. # ps ax|grep dump 11400 p1 I+ 0:00.97 /sbin/dump -0 -a -f usr.dump -L -h 0 -u /usr (dump) 11405 p1 I+ 0:00.18 dump: /dev/da0s1e: pass 4: 4.28% done, finished in 0:03 at Fri Aug 8 10:35:34 2008 (dump) 11406 p1 I+ 0:00.24 /sbin/dump -0 -a -f usr.dump -L -h 0 -u /usr (dump) 11407 p1 I+ 0:00.24 /sbin/dump -0 -a -f usr.dump -L -h 0 -u /usr (dump) 11408 p1 I+ 0:00.23 /sbin/dump -0 -a -f usr.dump -L -h 0 -u /usr (dump) top shows 11400 in wait state, 11406-11408 in pause state and 11405 in sbwait state. Any hint is appreciated. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dump locks again
Andrea Venturoli wrote: Hello. I googled around for this but found only very old threads (from 2005 or so). I'm taking dumps of a new box I build, which runs 7.0/amd64 on 8 cores with harware RAID-5 (ciss driver). This is an example of the command I issue: dump -0 -a -f usr.dump -L -h 0 -u /usr Almost always, the dump process will work up to Pass IV (regular files), but then stuck there. # ps ax|grep dump 11400 p1 I+ 0:00.97 /sbin/dump -0 -a -f usr.dump -L -h 0 -u /usr (dump) 11405 p1 I+ 0:00.18 dump: /dev/da0s1e: pass 4: 4.28% done, finished in 0:03 at Fri Aug 8 10:35:34 2008 (dump) 11406 p1 I+ 0:00.24 /sbin/dump -0 -a -f usr.dump -L -h 0 -u /usr (dump) 11407 p1 I+ 0:00.24 /sbin/dump -0 -a -f usr.dump -L -h 0 -u /usr (dump) 11408 p1 I+ 0:00.23 /sbin/dump -0 -a -f usr.dump -L -h 0 -u /usr (dump) top shows 11400 in wait state, 11406-11408 in pause state and 11405 in sbwait state. Any hint is appreciated. This was fixed in 7.0-STABLE. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dump locks again
Kris Kennaway ha scritto: This was fixed in 7.0-STABLE. Kris Thanks Kris. Since this is a critical production box, I'm a bit scared to track Stable. Do you know when this will be merged into a release (7.1 I suppose)? Would it be safer to just get this single patch (if possible at all)? I've also been advised (off list), to switch from the default 4BSD scheduler to ULE. What are the implications of this? Would it solve this specific problem or would I still need to patch/upgrade? bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dump locks again
Andrea Venturoli wrote: Kris Kennaway ha scritto: This was fixed in 7.0-STABLE. Kris Thanks Kris. Since this is a critical production box, I'm a bit scared to track Stable. Do you know when this will be merged into a release (7.1 I suppose)? I don't know if it is planned to merge the fix as a 7.0 erratum. You could ask re@ about their plans if you like. Would it be safer to just get this single patch (if possible at all)? Perhaps but I don't have a patch handy. I've also been advised (off list), to switch from the default 4BSD scheduler to ULE. What are the implications of this? Better performance, most likely. Would it solve this specific problem or would I still need to patch/upgrade? No, it won't solve it. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
