docs:vserver
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
docs:vserver [2015-10-05 14:25] – arekm | docs:vserver [2015-10-05 15:07] (current) – syn on glen | ||
---|---|---|---|
Line 722: | Line 722: | ||
That's because vserver patch for kernels earlier than 2.6.23 patched xfs filesystem to introduce new flag: | That's because vserver patch for kernels earlier than 2.6.23 patched xfs filesystem to introduce new flag: | ||
- | < | + | < |
#define XFS_XFLAG_BARRIER | #define XFS_XFLAG_BARRIER | ||
</ | </ | ||
+ | |||
+ | 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. | Starting with kernel 2.6.23 kernel introduced filestreams which are using 0x00004000 bit, thus causing conflict with vserver. | ||
- | < | + | < |
#define XFS_XFLAG_FILESTREAM | #define XFS_XFLAG_FILESTREAM | ||
</ | </ | ||
Line 734: | Line 736: | ||
Vserver stopped adding such xfs xflag in 3.13 BUT your existing filesystem can still have XFS_XFLAG_BARRIER (0x00004000) set | 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. | causing oops in newer kernels. | ||
+ | |||
+ | How to find out if I'm affected? | ||
+ | |||
+ | IIF you don't use filestream feature then modify http:// | ||
+ | |||
+ | <file diff> | ||
+ | diff --git a/ | ||
+ | index 4e22ecd..887512f 100644 | ||
+ | --- a/ | ||
+ | +++ b/ | ||
+ | @@ -34,19 +34,21 @@ dotime(void *ti, char *s) | ||
+ | void | ||
+ | | ||
+ | { | ||
+ | - | ||
+ | - (long long)sp-> | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | - | ||
+ | + if (sp-> | ||
+ | + | ||
+ | + (long long)sp-> | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + | ||
+ | + } | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | and then run it with mounted directory of each filesystem (bstat /; bstat /home etc). It will print "ino ..." information for filestream files. | ||
+ | |||
+ | |||
+ | How to clean up? | ||
+ | |||
+ | rsync files to other partition, recreate problematic partition and then copy files back. | ||
===== Debian or Ubuntu guest installation ===== | ===== Debian or Ubuntu guest installation ===== |
docs/vserver.1444047949.txt.gz · Last modified: 2015-10-05 14:25 by arekm