On Sat, Sep 13, 2014 at 04:41:00PM +0200, Toralf Förster wrote:
> On 09/01/2014 03:41 PM, Liu Bo wrote:
> > I believe that this warning of btrfs_evict_inode also comes from a result of
> > lseek, and Chris said that he's prepared a fix for that, so it's queued in
> > the
> > next version.
> >
> >
On 09/01/2014 03:41 PM, Liu Bo wrote:
> I believe that this warning of btrfs_evict_inode also comes from a result of
> lseek, and Chris said that he's prepared a fix for that, so it's queued in the
> next version.
>
> thanks,
> -liubo
So rather fixed in -rc6 because v3.17-rc4-337-gfc486b0 still s
On Mon, 1 Sep 2014 09:37:54 PM Toralf Förster wrote:
> Ah thx, it seems that fix does not made it in -rc3, so -rc4 would be a
> better choice for a re-test, or ?
It all depends on what Chris Mason sends to Linus, and what Linus chooses to
accept.
Your best bet is to watch the mailing list for t
On 09/01/2014 03:41 PM, Liu Bo wrote:
> I believe that this warning of btrfs_evict_inode also comes from a result of
> lseek, and Chris said that he's prepared a fix for that, so it's queued in the
> next version.
>
> thanks,
> -liubo
Ah thx, it seems that fix does not made it in -rc3, so -rc4 wo
On Fri, Aug 29, 2014 at 11:12:28PM +0200, Toralf Förster wrote:
> At as 32 bit KVM I run these 2 commands:
>
> tfoerste@n22kvm ~ $ mkdir /mnt/ramdisk/btrfs; truncate -s 97M
> /mnt/ramdisk/btrfs.fs; /sbin/mkfs.btrfs /mnt/ramdisk/btrfs.fs; sudo su -c
> "mount -o loop,compress=lzo /mnt/ramdisk/btrf
