On Sun, Feb 26, 2017 at 10:47:40AM +0530, Bhasker C V wrote:
> I compiled kernel 4.10 and I can confirm it is working fnie now. 4.10
> has the compat-ioctl patches for btrfs progs to work with x86_64
> kernel in i386 userland.
So does 4.9.10 if you prefer running long-lived releases.
--
I compiled kernel 4.10 and I can confirm it is working fnie now. 4.10
has the compat-ioctl patches for btrfs progs to work with x86_64
kernel in i386 userland.
thanks to all
On Sun, Feb 26, 2017 at 2:10 AM, Hans van Kranenburg
wrote:
> On 02/25/2017 08:30 PM,
On 02/25/2017 08:30 PM, Bhasker C V wrote:
> Hi all,
>
> I have an x86_64 kernel running with i386 userland rootfs.
Which kernel version? (`uname -a`)
> Long back I believe there were some fixes for btrfs-tools which ran
> smoothly in this setup but after several dist-upgrades(debian) and
>
Hi all,
I have an x86_64 kernel running with i386 userland rootfs.
Long back I believe there were some fixes for btrfs-tools which ran
smoothly in this setup but after several dist-upgrades(debian) and
long forgotten command, the btrfs-tools commands have started to fail
for instance
$ sudo
> On Feb 23, 2017, at 7:15 PM, Hans van Kranenburg
> wrote:
>
> On 02/23/2017 05:42 PM, Kenneth Bogert wrote:
>>
>>> On Feb 17, 2017, at 1:39 PM, Kenneth Bogert wrote:
>>>
>>> On Feb 11, 2017, at 12:34 PM, Kenneth Bogert
Hey guys,
I believe I have seen a OOM situations reported on the ML and IRC
recently, both of
which are believed to be unrelated to btrfs, which this case is probably
as well; I just
want to provide my dmesg here anyway in case it turns out to be related
to btrfs
nonetheless.
The following
Dear Qu,
any news on your branch? I still don't see it merged anywhere.
Greets,
Stefan
Am 04.01.2017 um 17:13 schrieb Stefan Priebe - Profihost AG:
> Hi Qu,
>
> Am 01.01.2017 um 10:32 schrieb Qu Wenruo:
>> Hi Stefan,
>>
>> I'm trying to push it to for-next (will be v4.11), but no response yet.