>>>>> " " == bug1 <bug1@netconnect.com.au> writes:
> Goswin Brederlow wrote:
>> I'm using 2.4.0-test1-ac7 and also have problems with loopback
>>
>> losetup -d /dev/loop/XXX
>>
>> leaves the file attached to that device somehow locked. You
>> cannot open it for write anymore (while you can open it for
>> write while it is attached).
>>
>> You also can't reatach the file to a loopback anymore.
>>
>> So I wonder how you reintegrate the file into your raid. Your
>> "losetup /dev/loop/XXX file" call should fail (unless the bug
>> was partly fixed).
>>
>> MfG Goswin
> hmm, im not sure i exactly i follow you.
> In 2.2.15, 2.4.0-test1-ac18 and 2.4.0-test1-ac20 i can do
> losetup /dev/loop1 ./loop1fs
> losetup -d /dev/loop1 (as long as nothign is using ./loop1fs)
> losetup /dev/loop1 then says the device is not configured,
> which is correct.
Try anoter
$ losetup /dev/loop1 ./loop1fs
after those commands, or try
$ echo foo >loop1fs
That then doesn't work anymore with 2.4.0-test1-ac7.
> So i can remove and reintegrate /dev/loop1 and then remove
> /dev/loop2 but get errors reintegrating it. If i remove and
> reintegrate /dev/loop2 first i can remove /dev/loop1 but not
> reintegrate it.
> This is the error i get, it doesnt look like a very good trace,
> but anyway.
Seems to be unrelated.
MfG
Goswin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:20 EST