Package: util-vserver
Severity: minor
Hello
On Mon, Oct 03, 2005 at 01:42:36PM +0800, Andrew Lee wrote:
> Hi Ola,
>
> ?b 2005/10/3 ?W?? 3:39 ???AOla Lundqvist ?g???G
>
> >Now I have run the entire test suite...
> >
> >zircone:/srv/vservers/labradorit/root# ./testfs.sh -l -t -D /dev/
> >loop4 -M /mnt/t
> >Linux-VServer FS Test [V0.09] Copyright (C) 2005 H.Poetzl
> >Linux 2.4.27-mppe+ctx+vlan-686-smp i686/0.30.204
> >VCI: <none> (unknown)
>
> Sorry, it's my fault again, I didn't mention all the steps.
> You should make a loopback file and run losetup /dev/loop4
> loopbackfile before run the testfs.sh script.
> The VCI shouldn't be <none> if you have setup /dev/loop4 correctly, I
> did same thing and got same errors when I forgot to setup the /dev/
> loop4 after a reboot.
>
> Here is what I did for create a loopback file and the run losetup:
> # dd bs=1024k count=1024 if=/dev/zero of=1gb.testfile
> # losetup /dev/loop4 1gb.testfs
> Note: I have other loopback files running on /dev/loop{0,1,2,3}
> already, so I use /dev/loop4 in my case.
>
> Very sorry for made your confused. Could you please test it again?
> I think the testfs.sh script will give you information of VCI and do
> the real checks on each task after you setup /dev/loop4 correctly.
> If the testfs.sh give you fails on 109 and 121, that can confirm this
> is bug.
> For other fails, you may ask Bertl, cause upstream author knows much
> more than me, also much better than I forward your questions to him. :)
>
> I suggest to put or mention these test tasks in util-vserver package
> for our users to make sure the vserver patch+tools work properly.
> Should I create another report as wistlist or only mentioned here is
> enough?
Good Idea. Filing a new bug about this now.
Regards,
// Ola
> Regards,
>
> -Andrew
>
--
--------------------- Ola Lundqvist ---------------------------
/ [EMAIL PROTECTED] Annebergsslingan 37 \
| [EMAIL PROTECTED] 654 65 KARLSTAD |
| +46 (0)54-10 14 30 +46 (0)70-332 1551 |
| http://www.opal.dhs.org UIN/icq: 4912500 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
