Hello Ian, "Ian Stakenvicius, Aerobiology Research": > A few various directories within the filesystem are being erroneously > copied-up(?? i don't know the word for this) to the tmpfs for no > apparent reason and are virtually empty in comparison with the contents > of the nfsroot. Which directories these are seem to change every > reboot.. Example:
Let's make sure whether the copyup is happend expectedly or not. This patch is for debug-print which dumps the stacktrace when copyup for a dir happens. Apply it and save all the logs, and we will know why the dir was copied-up. > Usually, if I say, want to try and recompile a kernel -- everything's > fine to begin with. > > cd /usr/src/linux ; make oldconfig > > After that completes, /mnt/initrd/mnt/ramdisk/usr/src/include/linux may > (usually but not always) exists and is usually empty or nearly empty. > The parent dir only holds a subdir 'linux'. This effectively nullifies > /usr/src/linux/include/linux which makes the next stage of compiling a > kernel rather difficult. The scenario in this case MAY be something like this. - a file under /usr/src/linux is newly created or modified (and copied-up). - the file was removed (a whiteout for that will be created if the file was not newly created). - then /usr/src/linux will be left as empty. You will be able to confirm this scenario by "strace -f -o /tmp/s -e trace=unlink,rmdir make oldconfig" and the whiteout under /usr/src/linux. J. R. Okajima
a.patch.bz2
Description: BZip2 compressed data
------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo
