Unable to create a directory with mkdir

Using applications, configuring, problems
Message
Author
User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#16 Post by Semme »


stelvio03
Posts: 19
Joined: Fri 08 Feb 2013, 07:33

#17 Post by stelvio03 »

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

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#18 Post by Semme »

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..

stelvio03
Posts: 19
Joined: Fri 08 Feb 2013, 07:33

#19 Post by stelvio03 »

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..
Tonight I'll try.

Thank you

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#20 Post by Karl Godt »

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) .

Code: Select all

type -a mkdir
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" .

stelvio03
Posts: 19
Joined: Fri 08 Feb 2013, 07:33

#21 Post by stelvio03 »

stelvio03 wrote:
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..
Tonight I'll try.

Thank you
I tried, but without success.
I tried mkdir /tmp/empty and it works perfectly.

Feel free to suggest me every possibile, but sensible, test I can run on the hdd frugal installation.

Thank you

Andrea

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#22 Post by Semme »

Your response is misleading. Ext3 without success?

Make dir works? Under what conditions?
I tried, but without success. I tried mkdir /tmp/empty and it works perfectly.
==

Which program created the partitions here:
2 NTFS and 1 FAT32

stelvio03
Posts: 19
Joined: Fri 08 Feb 2013, 07:33

#23 Post by stelvio03 »

Semme wrote:Your response is misleading. Ext3 without success?

Make dir works? Under what conditions?
I tried, but without success. I tried mkdir /tmp/empty and it works perfectly.
==

Which program created the partitions here:
2 NTFS and 1 FAT32
Sorry for the misleading answer.
1. Ext3 didn't solve the problem.
2. mkdir /tmp/empty worked under the same conditions mkdir /var/empty .
3. I think it was done a lot of time ago with windows disk management tool
4. I have a doubt: after I created the ext3 savefile, I copied all the content from the old ext2 savefile to the new ext3.

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#24 Post by Semme »

I don't know Pup intimately enough to say whether your issue's Pups layering system or the kernel itself.

Perhaps you need some kind of patch.. something Rerwin was getting at? I don't have an explanation.

Were you hinting at something here? Those badblocks links I left should cover the bases..
Feel free to suggest me every possibile, but sensible, test I can run..
Furthermore, you'll wanna run any of those from a *live* boot: puppy pfix=ram

stelvio03
Posts: 19
Joined: Fri 08 Feb 2013, 07:33

#25 Post by stelvio03 »

I solved the problem.
I created a new savefile (ext2), increased the size, and then I copied the content of the old savefile to the new one, except the /var directory.
It works without any problem.
Is there an automated way to copy data from a savefile to another ?
I noticed that when I shutdown the system, there some error regarding (loop) ext2 sync ....
I couldn't read, because they are displayed very fast.

User avatar
tallboy
Posts: 1760
Joined: Tue 21 Sep 2010, 21:56
Location: Drøbak, Norway

#26 Post by tallboy »

I believe the dirname /var/empty/ may be locked or reserved in some way.

You should check if you can make a directory in /var/ with another name.

I actually have an empty /var/empty/ dir in my LupuPlus_528, and looking at the date of creation, it is identical with some other version build dates back in 2010.

tallboy
True freedom is a live Puppy on a multisession CD/DVD.

Post Reply