I've got a really unique problem. Running xeno-bk changeset 1364, I get
random filesystem/bash globbing problems in dom0. Same system under 2.4.26
without xeno, no issues at all.
In this case the dom0 distribution is slackware, running ext3, on an Adaptec
AIC-7892P U160/m scsi controller.
The problem manifests itself most easily with 'ls':
"""
root@durandal:~# ls /var/adm/packages/
aaa_base-10.0.0-noarch-1 guile-1.6.4-i486-1
pango-1.4.0-i486-1
aaa_elflibs-9.2.0-i486-1 gzip-1.3.3-i386-2
pciutils-2.1.11-i486-5
acpid-1.0.3-i486-1 hdparm-5.5-i486-1 pcre-4.5-i486-2
...
"""
works as expected.
"""
root@durandal:~# ls /var/adm/packages/*
: : No such file or directory
: : No such file or directory
...
"""
fails, as does:
"""
root@durandal:~# cd /var/log/packages/
root@durandal:/var/log/packages# ls *
: : No such file or directory
...
"""
Now things get really strange:
"""
root@durandal:/var/log/packages# for x in *; do echo $x; done
aaa_base-10.0.0-noarch-1
aaa_elflibs-9.2.0-i486-1
acpid-1.0.3-i486-1
at-3.1.8-i486-2
...
root@durandal:/var/log/packages# echo *
aaa_base-10.0.0-noarch-1 aaa_elflibs-9.2.0-i486-1 acpid-1.0.3-i486-1
...
root@durandal:/var/log/packages# ls `echo *`
: : No such file or directory
: : No such file or directory
...
root@durandal:/var/log/packages# strace ls *
: : command not found
root@durandal:/var/log/packages# cd
root@durandal:# strace ls /var/log/packages/*
: : command not found
root@durandal:~# ls *
/usr/bin/ls: *: No such file or directory
root@durandal:~# strace ls *
execve("/usr/bin/ls", ["ls", "*"], [/* 28 vars */]) = 0
brk(0) = 0x805a000
...
stat64("*", 0x805b6f4) = -1 ENOENT (No such file or directory)
lstat64("*", 0x805b6f4) = -1 ENOENT (No such file or directory)
write(2, "ls: ", 4ls: ) = 4
write(2, "*", 1*) = 1
open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such
file or directory)
write(2, ": No such file or directory", 27: No such file or directory) = 27
write(2, "\n", 1
"""
So strace only works in SOME of the directories that exhibit this problem,
and when it fails, it's really trying to stat a literal '*' - the bash globbing
fails randomly.
Normally I'd accept this as being a borked install that I'm trying to run as
dom0, but none of this behavior exhibits itself under the 2.4.26 stock kernel.
I did a make clean and a fresh make world to be sure I didn't have any old
object files laying around, no change in the behavior. The filesystem fsck -f's
clean under both xeno and non-xeno.
-m
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home