syn on --- https://www.pld-linux.org/docs/vserver?rev=1444048851 +++ https://www.pld-linux.org/docs/vserver?rev=1444050433 @@ -720,17 +720,17 @@ (or other filestream related function). That's because vserver patch for kernels earlier than 2.6.23 patched xfs filesystem to introduce new flag: - <file> + <file c> #define XFS_XFLAG_BARRIER 0x00004000 /* chroot() barrier */ </file> and files/dirs with such flag got saved on your filesystem. Starting with kernel 2.6.23 kernel introduced filestreams which are using 0x00004000 bit, thus causing conflict with vserver. - <file> + <file c> #define XFS_XFLAG_FILESTREAM 0x00004000 /* use filestream allocator */ </file> Vserver stopped adding such xfs xflag in 3.13 BUT your existing filesystem can still have XFS_XFLAG_BARRIER (0x00004000) set @@ -739,9 +739,9 @@ How to find out if I'm affected? IIF you don't use filestream feature then modify http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfstests.git;a=blob_plain;f=src/bstat.c;hb=HEAD to show only files containing XFS_XFLAG_FILESTREAM - <file> + <file diff> diff --git a/src/bstat.c b/src/bstat.c index 4e22ecd..887512f 100644 --- a/src/bstat.c +++ b/src/bstat.c
Diff URL: https://www.pld-linux.org/docs/vserver?do=diff&r1=1444048851&r2=1444050433 -- This mail was generated by DokuWiki at https://www.pld-linux.org/ _______________________________________________ pld-cvs-commit mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
