Debian Bug report logs - #862271
zfs-linux: loop mounted files on zfs are read-only

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Vladislav Kurz <vladislav.kurz@webstep.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: zfs-linux: loop mounted files on zfs are read-only

Date: Wed, 10 May 2017 15:43:43 +0200

Package: zfs-linux
Severity: normal

Dear Maintainer,

loop mounted files on ZFS are read only:

$ truncate -s 64G filesystem.img
$ mkfs.ext4 filesystem.img
$ mount -o loop filesystem.img /mnt
$ touch /mnt/test
touch: cannot touch ‘/mnt/test’: Read-only file system
$ mount -o remount,rw /mnt/
mount: cannot remount /dev/loop0 read-write, is write-protected

checking with mount, losetup shows that the loop filesystem is read only
It seems to be fixed upstream, please update to 0.6.5.10
https://github.com/zfsonlinux/zfs/issues/5776

Best Regards
Vladislav Kurz

Message #10 received at 862271@bugs.debian.org (full text, mbox, reply):

From: Aron Xu <aron@debian.org>

To: Vladislav Kurz <vladislav.kurz@webstep.net>, 862271@bugs.debian.org

Subject: Re: [Pkg-zfsonlinux-devel] Bug#862271: zfs-linux: loop mounted files on zfs are read-only

Date: Thu, 11 May 2017 17:28:49 +0800

On Wed, May 10, 2017 at 9:43 PM, Vladislav Kurz
<vladislav.kurz@webstep.net> wrote:
> Package: zfs-linux
> Severity: normal
>
> Dear Maintainer,
>
> loop mounted files on ZFS are read only:
>
> $ truncate -s 64G filesystem.img
> $ mkfs.ext4 filesystem.img
> $ mount -o loop filesystem.img /mnt
> $ touch /mnt/test
> touch: cannot touch ‘/mnt/test’: Read-only file system
> $ mount -o remount,rw /mnt/
> mount: cannot remount /dev/loop0 read-write, is write-protected
>
> checking with mount, losetup shows that the loop filesystem is read only
> It seems to be fixed upstream, please update to 0.6.5.10
> https://github.com/zfsonlinux/zfs/issues/5776
>

I confirm the problem. Release team is not likely to allow 0.6.5.10 to
enter testing, but we can try to push specific patches to fix it.

Regards,
Aron

Message #15 received at 862271-done@bugs.debian.org (full text, mbox, reply):

From: Aron Xu <aron@debian.org>

To: 862271-done@bugs.debian.org

Subject: Fixed in 0.6.5.10-1

Date: Mon, 5 Mar 2018 16:55:30 +0800

Source-Version: 0.6.5.10-1

This has been addressed in 0.6.5.10-1 package, closing for now.

Regards,
Aron

Message #20 received at 862271@bugs.debian.org (full text, mbox, reply):

From: Vladislav Kurz <vladislav.kurz@webstep.net>

To: 862271@bugs.debian.org

Subject: Re: Bug#862271 closed by Aron Xu <aron@debian.org> (Fixed in 0.6.5.10-1)

Date: Wed, 7 Mar 2018 11:01:23 +0100

On 03/05/18 09:57, Debian Bug Tracking System wrote:
> This has been addressed in 0.6.5.10-1 package, closing for now.

Hello,

I cannot see 0.6.5.10-1 in any archive. Is there any chance it will get
into jessie-backports and stretch?

-- 
Best Regards
        Vladislav Kurz

Message #25 received at 862271@bugs.debian.org (full text, mbox, reply):

From: Aron Xu <aron@debian.org>

To: Vladislav Kurz <vladislav.kurz@webstep.net>, 862271@bugs.debian.org

Subject: Re: [Pkg-zfsonlinux-devel] Bug#862271: closed by Aron Xu <aron@debian.org> (Fixed in 0.6.5.10-1)

Date: Wed, 7 Mar 2018 20:04:26 +0800

On Wed, Mar 7, 2018 at 6:01 PM, Vladislav Kurz
<vladislav.kurz@webstep.net> wrote:
> On 03/05/18 09:57, Debian Bug Tracking System wrote:
>> This has been addressed in 0.6.5.10-1 package, closing for now.
>
> Hello,
>
> I cannot see 0.6.5.10-1 in any archive. Is there any chance it will get
> into jessie-backports and stretch?
>

We have 0.7.4-1~bpo8+1 in jessie-backports-sloppy and 0.7.5-1~bpo9+1
in stretch-backports that have this fix included.

Regards,
Aron

Send a report that this bug log contains spam.