I'm trying to create a dir under var (mkdir /var/empty) but the system returns an error (mkdir: can't create directory '/var/empty': Input/output error). With dmesg I found this: aufs au_lkup_dentry:273:mkdir[5375]: I/O Error, both of real entry and whiteout found, empty, err -5.
I'm running a frugal install of slacko 5.5, but I had the same problem with 5.4.
My savefile is 574 MB large with 356 MB free.
This is the output of df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 33G 20G 14G 60% /initrd/mnt/dev_save
/dev/loop1 574M 219M 356M 39% /initrd/pup_rw
/dev/loop0 160M 160M 0 100% /initrd/pup_ro2
/dev/loop4 48M 48M 0 100% /initrd/pup_ro4
/dev/loop5 34M 34M 0 100% /initrd/pup_ro5
/dev/loop6 37M 37M 0 100% /initrd/pup_ro6
/dev/loop7 14M 14M 0 100% /initrd/pup_ro7
/dev/loop8 60M 60M 0 100% /initrd/pup_ro8
unionfs 574M 219M 356M 39% /
tmpfs 250M 308K 250M 1% /tmp
shmfs 241M 0 241M 0% /dev/shm
/dev/sda3 112G 106G 6.4G 95% /mnt/sda3.
I also tried e2fsck -p /mnt/home/boxpup/pup_save.2fs with success.
Does anyone have any idea ?
Thank you
Andrea
Unable to create a directory with mkdir
I am guessing hidden *.wh.* files in /initrd/pup_rw or /initrd/pup_ro1 .
/initrd/pup_rw is used in pupmode 12 frugal to HDD
and /initrd/pup_ro1 in pupmode 13 on USB flash pen drive.
Find them with rox clicked on the eye to show hidden files and delete them.
/initrd/pup_rw is used in pupmode 12 frugal to HDD
and /initrd/pup_ro1 in pupmode 13 on USB flash pen drive.
Find them with rox clicked on the eye to show hidden files and delete them.
«Give me GUI or Death» -- I give you [[Xx]term[inal]] [[Cc]on[s][ole]] .
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P
I deleted the *.wh.* files in /initrd/pup_rw, but the same error occured. If I launch the same slacko from usb key, I can create /var/empty without any problem.Karl Godt wrote:I am guessing hidden *.wh.* files in /initrd/pup_rw or /initrd/pup_ro1 .
/initrd/pup_rw is used in pupmode 12 frugal to HDD
and /initrd/pup_ro1 in pupmode 13 on USB flash pen drive.
Find them with rox clicked on the eye to show hidden files and delete them.
as well as a question.As I wrote in the previuos posts, the savefile filesystem has been checked successfully: so tonight I will do a full check of the filesystem on which I put the frugal install.Semme wrote:Rethinking your post, I'd say your problem is most likely related to this.
By then you may wanna run badblocks:
https://wiki.archlinux.org/index.php/Badblocks
http://linuxpoison.blogspot.com/2008/01 ... s-and.html
http://go2linux.garron.me/linux/2010/11 ... blocks-842
https://wiki.archlinux.org/index.php/Badblocks
http://linuxpoison.blogspot.com/2008/01 ... s-and.html
http://go2linux.garron.me/linux/2010/11 ... blocks-842
Yesterday evening I made some tests.
Here are the results:
1. the DU command works perfectly.
2. No bad blocks on the HDD
3. I moved the frugal installation directory to three different partitions (2 NTFS and 1 FAT32) trying the mkdir /var/empty command, but the result was always the same "aufs au_lkup_dentry:273:mkdir[5375]: I/O Error, both of real entry and whiteout found, empty, err -5".
4. If I run the same slacko "installation" from a FAT32 usbkey there's no error
Here are the results:
1. the DU command works perfectly.
2. No bad blocks on the HDD
3. I moved the frugal installation directory to three different partitions (2 NTFS and 1 FAT32) trying the mkdir /var/empty command, but the result was always the same "aufs au_lkup_dentry:273:mkdir[5375]: I/O Error, both of real entry and whiteout found, empty, err -5".
4. If I run the same slacko "installation" from a FAT32 usbkey there's no error
Tonight I'll try.Semme wrote:For s&g's.. which brand of stick is it? Perhaps it's Pups layering system? Hmm..
If your first choice is to run Slacko from the hd, make your save file an ext3.
And make sure the Win drive's defragged before creation..
Thank you
Honestly I would not have any more ideas.
Semme is right to point to the very rare possibility of not enough free space in the pup-save-file with the du command .
I have one failing flashdrive until now , so badblocks might be a possibility , too .
Busybox commads are better than their reputation most of the times (losetup could be written not to depend on devices mentioned in /proc/partitions or before 1.20 acpid was occassionally looping using 100% CPU on one core) .
sh-3.00# type -a mkdir
mkdir is /bin/mkdir
sh-3.00# file /bin/mkdir
/bin/mkdir: symbolic link to `busybox'
is a possibility to check for commands in different locations , though i doubt that coreutils mkdir would handle this issue different .
Hmmm .. dunno, since Puppy usually is root : Maybe aufs handles permission things different with "IO error" instead of "permission denied" .
Semme is right to point to the very rare possibility of not enough free space in the pup-save-file with the du command .
I have one failing flashdrive until now , so badblocks might be a possibility , too .
Busybox commads are better than their reputation most of the times (losetup could be written not to depend on devices mentioned in /proc/partitions or before 1.20 acpid was occassionally looping using 100% CPU on one core) .
Code: Select all
type -a mkdirmkdir is /bin/mkdir
sh-3.00# file /bin/mkdir
/bin/mkdir: symbolic link to `busybox'
is a possibility to check for commands in different locations , though i doubt that coreutils mkdir would handle this issue different .
Hmmm .. dunno, since Puppy usually is root : Maybe aufs handles permission things different with "IO error" instead of "permission denied" .