On Sat, Mar 27, 2004 at 08:11:53PM +0100, Lars Braeuer wrote:
> I've had a problem when updating from 2.4.20ctx-17_quota to 2.4.24/vserver 
> 1.26 (+quota) two weeks ago.
> 
> The system hasn't been able to map the long unique uid's to usernames 
> anymore after booting the new kernel. For now we are using the old kernel 
> again and I'm kind of stuck in solving this problem.
> 
> The first thing that seemed weird to me, is that when listing the files 
> from outside the vserver, some files have a uid of 0 (root) and others have 
> a long uid (i.e. 458752) which also seems to map to root (inside the 
> vserver). Here's an example (listing via "ls -lagn /vserver/<name>"):
> 
> ...
> drwxr-x---    2 458752   458752       4096 Nov 19 02:08 service/
> drwxrwxrwt    3 0        0            8192 Mar 27 19:45 tmp/
> drwxr-xr-x   14 0        0            4096 Oct 16 11:36 usr/
> drwxr-xr-x   20 0        0            4096 Oct 15 01:38 var/

458752 = 7*65536 .. which suggests that you are using
a special context tagging mode, which isn't supported 
anymore (uid16/gid16 mode)

> The same listing from inside the vserver ("vserver <name> exec ls -lagn /"):
> 
> ...
> drwxr-x---    2 0        0            4096 Nov 19 02:08 service
> drwxrwxrwt    3 0        0            8192 Mar 27 19:45 tmp
> drwxr-xr-x   14 0        0            4096 Oct 16 11:36 usr
> drwxr-xr-x   20 0        0            4096 Oct 15 01:38 var
> 
> When updating to the new kernel the files with the long uid's are not 
> properly mapped anymore. We noticed this because mysql wouldn't start in 
> any of the 10 vservers on this system. After chown'ing the related 
> mysql.pid files and directories the mysql server started. But there are 
> tons of files with wrong uid's left, so this wouldn't be a solution, just a 
> temporary patch.

as I see it, you have two options to migrate to 2.4.25/vs1.27

a) change the context tagging of all files to xid=0
   - this can be done on the 'old' setup by using the
     old chctx tool, or by touching each file from the
     host context (xid = 0)
   - or with tagxid disabled, using a small script, 
     reading the uid/gid, cropping them to 16 bits
   - or by doing an xid agnostic backup (tar, dump)

b) converting the partition to the new context tagging
   - again a small script, reading the uid/gid, splitting 
     it into xid/uid/gid and reassembling them to one of 
     the newer formats ...
   
> I wasn't able to test this issue anymore, because it's on a production 
> system. I'll be starting another try next week, so if there are any other 
> things I could check, please tell me.

> Thanks in advance for your help.

> Regards,
> 
> Lars

HTH,
Herbert

_______________________________________________
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to