docs:vserver
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
docs:vserver [2014-05-13 18:33] – Links to thinfo changed to th glen | docs:vserver [2015-10-05 15:07] (current) – syn on glen | ||
---|---|---|---|
Line 15: | Line 15: | ||
===== Installing Vserver host on PLD Linux ===== | ===== Installing Vserver host on PLD Linux ===== | ||
- | vserver support is included in PLD Linux main kernels, so you can just install kernel package | + | Ensure |
- | + | ||
- | < | + | |
- | # poldek -u kernel | + | |
- | </ | + | |
- | + | ||
- | or alternatively, | + | |
- | < | + | |
- | # poldek -u kernel-longterm | + | |
- | </ | + | |
+ | You can check this from kernel config: | ||
+ | < | ||
+ | # modprobe configs | ||
+ | # zgrep CONFIG_VSERVER / | ||
+ | CONFIG_VSERVER=y | ||
+ | </ | ||
===== Installing guest PLD Linux Vserver ===== | ===== Installing guest PLD Linux Vserver ===== | ||
Line 65: | Line 62: | ||
If you need to use another combination, | If you need to use another combination, | ||
- | * pld-ac - [[:AcInfo|PLD 2.0 (Ac)]] | + | * pld-ac - [[:ac|PLD 2.0 (Ac)]] |
* pld-th - [[:th|PLD 3.0 (Th)]] | * pld-th - [[:th|PLD 3.0 (Th)]] | ||
Line 582: | Line 579: | ||
With recent [[package> | With recent [[package> | ||
- | To specify arch during guest creation, use '' | + | To specify arch during guest creation, use '' |
< | < | ||
Line 716: | Line 713: | ||
You need '' | You need '' | ||
+ | |||
+ | ==== 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 '' | ||
+ | (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 c> | ||
+ | #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. | ||
+ | |||
+ | <file c> | ||
+ | #define XFS_XFLAG_FILESTREAM | ||
+ | </ | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 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.1399998818.txt.gz · Last modified: 2014-05-13 18:33 by glen