Eric Sandeen wrote:
Sagar Borikar wrote:
Could you kindly try with my test? I presume you should see failure
soon. I tried this on
2 different x86 systems 2 times ( after rebooting the system ) and I saw
it every time.
Sure. Is there a reason you're doing this on a loopback file? That
probably stresses the vm a bit more, and might get even trickier if the
loopback file is sparse...
Initially I thought to do that since I didn't want to have a strict
allocation limit but
allowing allocations to grow as needed until the backing filesystem
runs out of free space
due to type of the test case I had. But then I dropped the plan and
created a non-sparse
loopback device. There was no specific reason to create loopback but as
it was
simplest option to do it.
But anyway, on an x86_64 machine with 2G of memory and a non-sparse 10G
loopback file on 2.6.24.7-92.fc8, your test runs w/o problems for me,
though the system does get sluggish. I let it run a bit then ran repair
and it found no problems, I'll run it overnight to see if anything else
turns up.
That will be great. Thanks indeed.
Sagar
-Eric
|