This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
docs:vserver [2015-04-14 19:02] glen [Installing Vserver host on PLD Linux] |
docs:vserver [2015-10-05 14:25] arekm |
||
---|---|---|---|
Line 713: | Line 713: | ||
You need ''CAP_AUDIT_CONTROL'' in ''bcapabilities'' and lower ''priority_boost'' to ''0'' in ''/etc/audit/auditd.conf'' | You need ''CAP_AUDIT_CONTROL'' in ''bcapabilities'' and lower ''priority_boost'' to ''0'' in ''/etc/audit/auditd.conf'' | ||
+ | |||
+ | ==== XFS filesystem - kernel upgrade causes xfs related oops (xfs_filestream_lookup_ag) ==== | ||
+ | |||
+ | After upgrading from 2.6-3.4 kernels (possibly other versions) to 3.18 (tested, possibly other versions) kernel ooppses | ||
+ | almost immediately after accessing some files on xfs filesystem with ''xfs_filestream_lookup_ag'' visible in stack trace | ||
+ | (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> | ||
+ | #define XFS_XFLAG_BARRIER 0x00004000 /* chroot() barrier */ | ||
+ | </file> | ||
+ | |||
+ | Starting with kernel 2.6.23 kernel introduced filestreams which are using 0x00004000 bit, thus causing conflict with vserver. | ||
+ | |||
+ | <file> | ||
+ | #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 | ||
+ | causing oops in newer kernels. | ||
===== Debian or Ubuntu guest installation ===== | ===== Debian or Ubuntu guest installation ===== |