Re: unable to write via nfs to aufs of zfs branches

2013-09-30 Thread Pui Yong Ng
On 30 Sep 2013 14:32, <[1]sf...@users.sourceforge.net> wrote: > > > Pui Yong Ng: > > - I'm unable to write via nfs to an aufs union of zfs branches. The > > file is created, but nothing is written to the file, and nfs reports > > errno -38 (ENOSYS). > > - Writing directly

Re: unable to write via nfs to aufs of zfs branches

2013-09-30 Thread sfjro
Pui Yong Ng: > You're right. Sorry I didn't notice this pertinent info - I think it is > because it was only produced once and I only checked the syslog after > various other log entries went in. > > What do these logs indicate? It means zfs doesn't implement aio_write() file operation, and aufs

Re: unable to write via nfs to aufs of zfs branches

2013-09-30 Thread Pui Yong Ng
On 30 Sep 2013 15:39, <[1]sf...@users.sourceforge.net> wrote: > It means zfs doesn't implement aio_write() file operation, and aufs > doesn't support such filesystem. [] > If you know anything about a zfs plan to implement aio_read/_write, > please let me know. Indeed. Armed

Re: aufs-mounts suddenly become readonly

2013-09-30 Thread sfjro
Florian Klink: > I use Arch Linux (amd64) using the "zen-kernel" (tree on zen-kernel.org, > linus' kernel plus some nice additional features like UKSM and aufs3). > The package is called "linux-zen" in Arch Linux. Now I am installing Arch Linux... > I hope the problem will automatically go away

Re: aufs-mounts suddenly become readonly

2013-09-30 Thread Florian Klink
[1]sf...@users.sourceforge.net: Florian Klink: I use Arch Linux (amd64) using the "zen-kernel" (tree on zen-kernel.org, linus' kernel plus some nice additional features like UKSM and aufs3). The package is called "linux-zen" in Arch Linux. Now I am installing Arch Linux... Just to test t

Re: aufs-mounts suddenly become readonly

2013-09-30 Thread Florian Klink
I tested it on a kernel with the FS_USERNS_MOUNT and USER_NS enabled, the problem persists. So it doesn't look like a bug of aufs, but still thanks for your help! Florian Am 30.09.2013 11:46, schrieb Florian Klink: [[1]1]sf...@users.sourceforge.net: Florian Klink: I use Arch L

Re: aufs-mounts suddenly become readonly

2013-09-30 Thread sfjro
Florian Klink: > Just to test the kernel? You can get the location of the git tree and > the default config from here: > https://aur.archlinux.org/packages/linux-zen/?setlang=en To find out who runs "remount,ro". I don't understand why you focused FS_USERNS_MOUNT. J. R. Okajima ---

Re: aufs-mounts suddenly become readonly

2013-09-30 Thread Florian Klink
sf...@users.sourceforge.net: > Florian Klink: >> Just to test the kernel? You can get the location of the git tree and >> the default config from here: >> https://aur.archlinux.org/packages/linux-zen/?setlang=en > To find out who runs "remount,ro". > I don't understand why you focused FS_USERNS_MOU

Re: aufs-mounts suddenly become readonly

2013-09-30 Thread sfjro
Florian Klink: > I think, it's the init system that did the remount-ro (a remount,ro of / > is done when you shutdown). I now updated to a newer version, (of > systemd) and the problem went magically away - seems like systemd now > properly detects when it's inside a container and doesn't remount,

Re: unable to write via nfs to aufs of zfs branches

2013-09-30 Thread sfjro
Pui Yong Ng: > I appreciate it if you have any ideas :) otherwise, perhaps I will try > non-nfs network file systems. Here is a patch for a new aufs mount option "noaiop". - apply the patch (to aufs source files) and rebuild your aufs module. - when you mount aufs with zfs branches, add a mount op

Re: Linux 3.11-rc7: loop_backing_file() is not defined

2013-09-30 Thread sfjro
sf...@users.sourceforge.net: > > Florian Klink: > > The error message also appears when both "aufs" and "loop" are compiled > > as a module. > > Hmm... > I am afraid we should consider all combinations of these. > - aufs (is/is not) a module > - the source files are from (aufs3-linux/aufs3-standalo

Re: Linux 3.11-rc7: loop_backing_file() is not defined

2013-09-30 Thread Florian Klink
Am 01.10.2013 03:28, schrieb sf...@users.sourceforge.net: > sf...@users.sourceforge.net: >> Florian Klink: >>> The error message also appears when both "aufs" and "loop" are compiled >>> as a module. >> Hmm... >> I am afraid we should consider all combinations of these. >> - aufs (is/is not) a modu