Hi Vincent

I'm just using root_fs that comes with clownix as the link to root_fs for Fedora5 is broken. Don't know much about clownix. Looks like I have no option but to reboot host OS.
 
I'd like to build a simple root_fs which is smaller but I wasn't successful.

thanks
Prasad



From: Unknown <vincent-perrier@club-internet.fr>
To: K D <kdcalif@yahoo.com>
Cc: David Moffatt <David.Moffatt@access-company.com>; user-mode-linux-user@lists.sourceforge.net
Sent: Monday, January 12, 2009 4:26:02 PM
Subject: Re: [uml-user] F_SETLK failed, file already locked by pid 0

Hello,
It seems that you are using the root_fs from the clownix.net web site,
because of the term "bulk". But why are you not using it with the
rest of the clownix stuff, it should simplify your work, and if it
does not, send me a mail, I can try to help.
Regards
Vincent Perrier


Le lundi 12 janvier 2009 à 16:02 -0800, K D a écrit :
> Thanks for your reply.
>
> I do see some zombies in my setup but I don't think they are related
> to this.
>
>  u1234-lnx linux-2.6.28$ ps aux | grep Z
> USER      PID %CPU %MEM  VSZ  RSS TTY      STAT START  TIME COMMAND
> user222  9400  0.0  0.0    0    0 ?        Zs  13:46  0:00
> [telnet] <defunct>
> user222  9438  0.0  0.0    0    0 ?        Zs  13:47  0:00
> [telnet] <defunct>
> user222  9495  0.0  0.0    0    0 ?        Zs  13:51  0:00
> [telnet] <defunct>
> u1234    10464  0.0  0.0  3828  664 pts/9    S+  15:54  0:00 grep Z
> u1234-lnx linux-2.6.28$
> u1234-lnx linux-2.6.28$
> u1234-lnx linux-2.6.28$
> u1234-lnx linux-2.6.28$ ./linux mem=128M ubda=../bulk_fedora/root_fs
> Locating the bottom of the address space ... 0x0
> Locating the top of the address space ... 0xc0000000
> Core dump limits :
>        soft - 0
>        hard - NONE
> Checking that ptrace can change system call numbers...OK
> Checking syscall emulation patch for ptrace...missing
> Checking for tmpfs mount on /dev/shm...OK
> Checking PROT_EXEC mmap in /dev/shm/...OK
> Checking for the skas3 patch in the host:
>  - /proc/mm...not found: No such file or directory
>  - PTRACE_FAULTINFO...not found
>  - PTRACE_LDT...not found
> UML running in SKAS0 mode
> Linux version 2.6.280 (u1234@infra-bld1) (gcc version 3.4.6 20060404
> (Red Hat 3.4.6-3)) #1 Tue Jan 6 23:26:29 PST 2009
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
> 32512
> Kernel command line: mem=128M ubda=../bulk_fedora/root_fs root=98:0
> PID hash table entries: 512 (order: 9, 2048 bytes)
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 126660k available
> Calibrating delay loop... 4377.80 BogoMIPS (lpj=21889024)
> Mount-cache hash table entries: 512
> Checking for host processor cmov support...Yes
> Checking that host ptys support output SIGIO...Yes
> Checking that host ptys support SIGIO on close...No, enabling
> workaround
> net_namespace: 288 bytes
> /usr/include/linux/aio_abi.h not present during build
> 2.6 host AIO support not used - falling back to I/O thread
> NET: Registered protocol family 16
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 4096 (order: 3, 32768 bytes)
> TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> TCP reno registered
> NET: Registered protocol family 1
> Checking host MADV_REMOVE support...<3>MADV_REMOVE failed, err = -22
> Can't release memory to the host - memory hotplug won't be supported
> mconsole (version 2) initialized on /users/u1234/.uml/9rN2i3/mconsole
> Host TLS support detected
> Detected host type: i386 (GDT indexes 6 to 9)
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> msgmni has been set to 247
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> TCP cubic registered
> NET: Registered protocol family 17
> Initialized stdio console driver
> Console initialized on /dev/tty0
> console [tty0] enabled
> Initializing software serial port version 1
> console [mc-1] enabled
> F_SETLK failed, file already locked by pid 0
> Failed to lock '../bulk_fedora/root_fs', err = 11
> Failed to open '../bulk_fedora/root_fs', errno = 11
> ubda: Can't open "../bulk_fedora/root_fs": errno = 11
> F_SETLK failed, file already locked by pid 0
> Failed to lock '../bulk_fedora/root_fs', err = 11
> Failed to open '../bulk_fedora/root_fs', errno = 11
> ubda: Can't open "../bulk_fedora/root_fs": errno = 11
> VFS: Cannot open root device "98:0" or unknown-block(98,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> 6200        4195328 ubda driver: uml-blkdev
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(98,0)
>
> EIP: 0073:[<002f97a2>] CPU: 0 Not tainted ESP: 007b:bffff660 EFLAGS:
> 00200246
>    Not tainted
> EAX: 00000000 EBX: 000028ec ECX: 00000013 EDX: 000028ec
> ESI: 000028e9 EDI: bffff8da EBP: bffff678 DS: 007b ES: 007b
> 0f85be64:  [<0806aebc>] show_regs+0xb4/0xb6
> 0f85be90:  [<08059b02>] panic_exit+0x25/0x3b
> 0f85bea0:  [<08086f89>] notifier_call_chain+0x2c/0x62
> 0f85bec0:  [<0808703b>] __atomic_notifier_call_chain+0x17/0x1c
> 0f85bedc:  [<08087055>] atomic_notifier_call_chain+0x15/0x17
> 0f85bef8:  [<08071c52>] panic+0x4b/0xcd
> 0f85bf10:  [<0804991d>] mount_block_root+0x107/0x11b
> 0f85bf64:  [<08049982>] mount_root+0x51/0x56
> 0f85bf78:  [<08049aac>] prepare_namespace+0x125/0x149
> 0f85bf80:  [<08049629>] kernel_init+0x83/0x8c
> 0f85bf98:  [<08064d72>] run_kernel_thread+0x38/0x42
> 0f85bfcc:  [<08057600>] new_thread_handler+0x8c/0xb9
> 0f85bffc:  [<00000000>] 0x0
>
> Segmentation fault
> u1234-lnx linux-2.6.28$
>
>
>
>
>
>
>
> ______________________________________________________________________
> From: David Moffatt <David.Moffatt@access-company.com>
> To: K D <kdcalif@yahoo.com>;
> user-mode-linux-user@lists.sourceforge.net
> Sent: Monday, January 12, 2009 3:47:30 PM
> Subject: RE: [uml-user] F_SETLK failed, file already locked by pid 0
>

>
> I don’t know if this is the cause but look for a zombie process.  I
> had something were A locked a file then forked B.  A was “kill -9”’d
> but not B.  Somehow the lock was still held.  The fix was “killall A;
> killall B”.    I think what happed was A was a zombie waiting for B to
> die so it could get its return code.  Either that or the file lock was
> inherited across the lock.  Yeah I know sounds wrong but it worked.
>

>
> --David
>

>
>                                   
> ______________________________________________________________________
> From: K D [mailto:kdcalif@yahoo.com]
> Sent: Monday, January 12, 2009 3:31 PM
> To: user-mode-linux-user@lists.sourceforge.net
> Subject: [uml-user] F_SETLK failed, file already locked by pid 0
>
>

>
> If I kill all tasks in that session I should see that file getting
> unlocked right? Can we write a small kernel module that finds/unlocks
> this file? Will that work? Is there any other way to get around this
> other than rebooting the box or making a copy of root_fs and using
> that for uml session?
>
> I've built uml with 2.6.28 sources and running this on 2.6.11 kernel.
>
> F_SETLK failed, file already locked by pid 0
> Failed to lock '../bulk_fedora/root_fs', err = 11
> Failed to open '../bulk_fedora/root_fs', errno = 11
> ubda: Can't open "../bulk_fedora/root_fs": errno = 11
> F_SETLK failed, file already locked by pid 0
> Failed to lock '../bulk_fedora/root_fs', err = 11
> Failed to open '../bulk_fedora/root_fs', errno = 11
> ubda: Can't open "../bulk_fedora/root_fs": errno = 11
> VFS: Cannot open root device "98:0" or unknown-block(98,0)
>
>
> thanks
>

>
>

>
>                                   
> ______________________________________________________________________
> From: Flavio <fbcyborg@gmail.com>
> To: K D <kdcalif@yahoo.com>
> Cc: user-mode-linux-user@lists.sourceforge.net
> Sent: Friday, January 2, 2009 2:34:00 AM
> Subject: Re: [uml-user] link broken:
> http://uml.nagafix.co.uk/FedoraCore5/FedoraCore5-x86-root_fs.bz2
>
> 2008/12/26 K D <kdcalif@yahoo.com>
> >
> > hi
> >
> > http://uml.nagafix.co.uk/FedoraCore5/FedoraCore5-x86-root_fs.bz2 is
> broken. can someone pl post a working link to fedora5 or later rootfs?
> >
> > thanks
>
> Hi,
>
> http://uml.nagafix.co.uk/ redirects to the Overseas Procedures &
> Surgery Ltd. website.
> Maybe it has been hacked by someone.
> That is the reason why you can't download the Fedora filesystem image.
>
> Flavio
>
>

>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user