[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: knoppix-halt, pump, and persistent $home



Fixed in 5.3... That's great! I can't wait to use it.

Without starting a bugs for 5.3 thread... I'll just put this one out
here. Just so you know about it Klaus. You probably already do.

This happens if I am using my persistent $home or just booting from
the dvd with nothing else added. Just a different /proc/#
I will put some other info in case it is needed/related to an
explanation. Ignoring Google results pointing to Ubuntu, I did not see
anything obviously related.

If I do an updatedb, I get some strange result. Something is pointing
to a non existent proc? I tried doing a few find commands myself, but
I could not get the same output.

root!tty1:/# updatedb
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/task/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory
/usr/bin/find: /proc/4096/fd/4: No such file or directory

root!tty1:/# ps -A
  PID TTY          TIME CMD
    1 ?        00:00:01 init
    2 ?        00:00:00 migration/0
    3 ?        00:00:00 ksoftirqd/0
    4 ?        00:00:00 watchdog/0
    5 ?        00:00:08 events/0
    6 ?        00:00:00 khelper
    7 ?        00:00:00 kthread
   41 ?        00:00:00 kblockd/0
   42 ?        00:00:00 kacpid
  125 ?        00:00:00 ata/0
  126 ?        00:00:00 ata_aux
  127 ?        00:00:00 kseriod
  153 ?        00:00:02 kswapd0
  154 ?        00:00:00 aio/0
  848 ?        00:00:00 kpsmoused
  906 ?        00:00:00 ksuspend_usbd
  909 ?        00:00:00 khubd
  982 ?        00:00:00 khpsbpkt
 1359 ?        00:00:00 aufsd
 1360 ?        00:00:00 aufsd
 1361 ?        00:00:00 aufsd
 1362 ?        00:00:00 aufsd
 1662 ?        00:00:00 udevd
 2618 ?        00:00:00 kgameportd
 2708 ?        00:00:00 ac97/0
 2727 ?        00:00:00 ac97/0
 2966 ?        00:00:00 dbus-daemon
 2986 ?        00:00:02 hald
 2987 ?        00:00:00 hald-runner
 3038 ?        00:00:00 hald-addon-acpi
 3059 ?        00:00:00 hald-addon-keyb
 3100 ?        00:00:00 hald-addon-stor
 3490 ?        00:00:00 pump
 3540 tty1     00:00:00 bash
 3541 tty2     00:00:00 bash
 3542 tty3     00:00:00 bash
 3543 tty4     00:00:00 bash
 3893 ?        00:00:00 pdflush
 3968 ?        00:00:00 pdflush
 4105 tty1     00:00:00 ps

root!tty1:/# mount
/dev/root on / type ext2 (rw)
/ramdisk on /ramdisk type tmpfs (rw,size=826960k,mode=755)
/UNIONFS on /UNIONFS type aufs (rw,br:/ramdisk:/KNOPPIX:/KNOPPIX2)
/dev/hdc on /cdrom type iso9660 (ro)
/dev/cloop on /KNOPPIX type iso9660 (ro)
/dev/cloop2 on /KNOPPIX2 type iso9660 (ro)
/proc/bus/usb on /proc/bus/usb type usbfs (rw,devmode=0666)
/dev/pts on /dev/pts type devpts (rw)

root!tty1:/# cat /etc/mtab
/dev/root / ext2 rw 0 0
/ramdisk /ramdisk tmpfs rw,size=826960k,mode=755 0 0
/UNIONFS /UNIONFS aufs rw,br:/ramdisk:/KNOPPIX:/KNOPPIX2 0 0
/dev/hdc /cdrom iso9660 ro 0 0
/dev/cloop /KNOPPIX iso9660 ro 0 0
/dev/cloop2 /KNOPPIX2 iso9660 ro 0 0
/proc/bus/usb /proc/bus/usb usbfs rw,devmode=0666 0 0
/dev/pts /dev/pts devpts rw 0 0



On 3/6/08, Klaus Knopper <debian-knoppix@knopper.net> wrote:
> On Wed, Mar 05, 2008 at 08:01:28PM -0500, John Woods wrote:
> > Hi everybody,
> >
> > This is a heads up to Klaus and company to address an issue where pump
> > leaves open files in /usr and /var. This causes any further remounts
> > of the persistent image(knoppix.img) after the very first one to cause
> > an fsck to clean up.
>
>
> This is already fixed in version 5.3 which should appear 1-2 weeks after
> Cebit on the mirrrors. Instead of pump -k, which may leave the network
> card in a "down" state, we simply kill pump, so the files in /var are
> closed, but the network stays intact until halt.
>
> -Klaus
>


Reply to: