reservation ran out?
I just created bug 849, about a reservation problem I'm seeing on my x86_64 system on ubuntu jaunty (2.6.28-15-generic).
http://oss.sgi.com/bugzilla/show_bug.cgi?id=849
Am I doin' something wrong, or is this a real problem?
- Gavin
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 6 lines · Gavin Peters
I just created bug 849, about a reservation problem I'm seeing on my
x86_64system on ubuntu jaunty (2.6.28-15-generic).http://oss.sgi.com/bugzilla/show_bug.cgi?id=849
Am I doin' something wrong, or is this a real problem?
Sounds like a real problem.
Any reproducible testcase?
-Eric
Quoted 1 line
- Gavin
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 4 lines · Eric Sandeen
Quoted 3 lines · Gavin Peters
I just created bug 849, about a reservation problem I'm seeing on my
x86_64system on ubuntu jaunty (2.6.28-15-generic).
Quoted 8 lines
Quoted 3 lines
http://oss.sgi.com/bugzilla/show_bug.cgi?id=849
Am I doin' something wrong, or is this a real problem?
Sounds like a real problem.
Any reproducible testcase?
Alas, no; I was running mythtv, and my disk was somewhat fragmented.
root@mythmaker:~# xfs_db -c frag -r /dev/sda7 actual 17379, ideal 98, fragmentation factor 99.44% root@mythmaker:~# xfs_db -c frag -r /dev/sdb1 actual 4268, ideal 53, fragmentation factor 98.76%
The disk that was having the trouble was sda7, my sdb1 was fine.
Mythtv fragments disks so badly by appending to two, or three files, simultaniously and fsyncing on them a lot. Perhaps some hacking at that will give a reproduction, I'll see if I can take the time and do that.
I've since defragmented both disks though; and I've set a large allocsize (512m) to prevent future fragmentation. We'll see if I get another crash.
- Gavin
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs