well, I'd use 2.6.1 just because it has a lot of fixes,
but when you make that loopback device, are you first
filling the loop file zeroed out from /dev/zero ?
As far as I know you can't make a dynamic loopback file
please correct me if I'm wrong on this :/
Also, what options were you passing to  mke2fs to create
the filesystem itself ??
I've never seen that error before.  The only time I saw
it is when I was running out of inodes on genkernel because
of the sheer number of small files the /dev filesystem creates
in ratio to the size of the fs itself :/
But if it works on subsequent tries, that doesn't make sense.

-Brad

> Hi guys,
>
> livecd-stage3 in catalyst is now completed (will commit in a minute.) I
> have one last thing to add -- a "livecd-stage3/prune" variable support
> for the spec file, and of course documentation.
>
> But right now I am getting held up by a kernel bug. I can mount a
> loopback fs, and try to copy files to it. I get a "no space left on
> device." I can then repeat the exact same cp command, and a few seconds
> later it works. Seems to be some weird synchronization bug in the
> kernel. I'm using gentoo-dev-sources-2.6.0 and I'm wondering if anyone
> has experienced anything similar. This is on amd64 but the loopback code
> in the kernel should be arch-independent.
>
> With this bug, sometimes the livecd-stage3 build works, and other times
> it will abort with "no space left on device." Not pleasant :/
>
> Regards,
>
> Daniel
>
>
> --
> gentoo-releng@g.o mailing list
>
>
>


--
gentoo-releng@g.o mailing list