On Thu, Sep 23, 2010, Amit Arora wrote:
> BTW, which file system is it ? From last I know, fallocate was
> supported on only ext4, ocfs and xfs.
It's probably the linaro-media-create default, ext3, which we should at
least bump to ext4 I guess.
--
Loïc Minier
_
On Thu, Sep 23, 2010 at 2:24 PM, Loïc Minier wrote:
> On Wed, Sep 22, 2010, Matt Waddel wrote:
>> fallocate01 1 TFAIL : fallocate(5, 0, 49152, 4096) failed:
>> TEST_ERRNO=EFBIG(27): File too large
>> fallocate01 2 TFAIL : fallocate(6, 1, 49152, 4096) failed:
>> TEST_ERRNO=EFBIG(27):
On Wed, Sep 22, 2010, Matt Waddel wrote:
> fallocate011 TFAIL : fallocate(5, 0, 49152, 4096) failed:
> TEST_ERRNO=EFBIG(27): File too large
> fallocate012 TFAIL : fallocate(6, 1, 49152, 4096) failed:
> TEST_ERRNO=EFBIG(27): File too large
> fallocate027 TFAIL : fallocate(tfil
On Wed, Sep 22, 2010 at 3:51 PM, Matt Waddel wrote:
> Hi,
>
> There are many failures in the LTP tests related to message
> queues. This is because the CONFIG_POSIX_MQUEUE option is
> disabled in the kernel. When I enable this option all the
> ltp mqueue tests pass. Does anyone know why we would
Hi,
There are many failures in the LTP tests related to message
queues. This is because the CONFIG_POSIX_MQUEUE option is
disabled in the kernel. When I enable this option all the
ltp mqueue tests pass. Does anyone know why we would want
this option to be disabled? It doesn't seem to add much to
