In a partition of 7.7G - 641M free.

[MrAccident]

I'm using Puppy for some time; I think it happened gradually.
I hardly installed anything; so I have no idea how that happen.
Can it be some garbage; which I can remove?

[nooby]

I'm using Puppy for some time; I think it happened gradually.
I hardly installed anything; so I have no idea how that happen.
Can it be some garbage; which I can remove?

Now I am not only a noob I am a know nothing.

So in case I am wrong others could look angry on me.

What it measure is available to the size one have given Puppy.
So that is why it looks so odd.

My solution and I learned it from others here is to link to a directory
on my /mnt/home/ so that way I have all the gigabites available.

One drag the directory and drop it as a symbolic link.
Most likely somebody has descripte it in some thread.

I did the same with a Cache that also could explain why it is so little room left.

Hope somebody comes along and find the link to that description.
I am on a chemo therapy so too tired to look things up. I apology for that.

[Semme]

Use GdMap to open and inspect the size of directories in /root.

[MrAccident]

In GDmap - Root shows 752mib.
I also see that Wine takes a big portion; and I UNINSTALLED it!

[MrAccident]

nooby - I don't know if I understood what you meant.
On the panel at the bottom (sorry, don't remember how it's called) - there's the symbol that shows some kind of a container that when there's a lot of free space - is green; and now it's red and flickering. When I click on it - it shows all the partitions. The partition Puppy resides in - has only 600+M left.

[Semme]

Your more likely to receive meaningful responses when including the Pup version and how you're installed.

Now aside from /proc, does this help clue you in?

Code: Select all

du -skh /* | sort -nr | head -10

[nooby]

nooby - I don't know if I understood what you meant.
On the panel at the bottom (sorry, don't remember how it's called) - there's the symbol that shows some kind of a container that when there's a lot of free space - is green; and now it's red and flickering. When I click on it - it shows all the partitions. The partition Puppy resides in - has only 600+M left.

Good that others also jumped in to be of bettr thelp than I can be.

When it has that staple that flicker then I trust that it could be the Cache
Dir getting full. So look for that one and empty it.

That is why I drag and drop a symbolic link
to the /mnt/home/ part of the partition.

I'm talking frugal install here. I know nothing
about other ways to have Puppy installed.

Use the search for to find that description it has graphics
showing how to do the drag and drop. I guess Semme
knows how to do such? Or else you have to wait for
somebody less tired than what I am for some weeks to come.

I'll have to leave you to your own resources now. Buzy
fighting the Cancer. Okay!

Check if this each can help you in he meantime somebody
hopefully fil in the gaps if yu fail to find that description.

Most likely it was published on the forum 2013 or my memory fails me.

I sign out from this thread and will not read further.

[MrAccident]

Nooby - I wish you a full recovery.
Couldn't find what you mean; and didn't really understood it.

The "Cache" folder seems empty; I checked it in GDmap.

Semme - the code doesn't do anything in the terminal; if that's what I was suppose to use it for.
Version - Slacko 5.7.0; full disk install.
I thought of what may be the cause of the problem - some time ago - there was an improper computer shot-down that messed up something in Puppy. From then - I couldn't shut it off from the menu; so I'm writing "busybox poweroff" or "busybox reboot" in terminal; and that also causes something improper; so when it boots up - it says something about an improper shut-down that occurred. So I think maybe Puppy doesn't do something that it suppose to do after the user chooses to shut it down, if it goes properly.

The FireFox option seemed to have made some video that I downloaded and was watching - disappear; so I reverted it.

[Semme]

Ahh, you probably don't have head. Try:

Code: Select all

du -h --max-depth=1 /

And if that's a full install on an ext2 filesystem, it may benefit from an fsck.

==

Code: Select all

fdisk -l

.. Shows your install partition as?

[MrAccident]

It's ext4

Code: Select all

# fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2d7a2d79

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    16181247     8089600   83  Linux
/dev/sda2        17408160  1953524159   968058000    5  Extended
/dev/sda3        16181248    17407999      613376   82  Linux swap / Solaris
/dev/sda5        17408223  1953524159   968057968+   7  HPFS/NTFS/exFAT

Partition table entries are not in disk order

Disk /dev/sdb: 320.1 GB, 320071851520 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625140335 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x09730972

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1       620994560   623912959     1459200   83  Linux
/dev/sdb2           16065   620992574   310488255    f  W95 Ext'd (LBA)
/dev/sdb3       623912960   625139711      613376   82  Linux swap / Solaris
/dev/sdb5   *       16128   620992574   310488223+   7  HPFS/NTFS/exFAT

Partition table entries are not in disk order

Code: Select all

# du -h --max-depth=1 /
3.7M	/sbin
100K	/audit
1.6M	/var

[Semme]

Nothing more, huh? Odd.. May be your problem's right there.

Should have something like this:

Code: Select all

4.8M	/bin
69M	/lib
287M	/root
4.0K	/boot
628K	/dev
7.4M	/etc
203M	/opt
16K	/lost+found
0	/sys
14G	/mnt
41M	/var
4.0K	/share
1.5G	/usr
13M	/sbin
0	/proc
393K	/tmp

So sda1's where your install is, correct? You have the disk to boot a "live" session?

[MrAccident]

Yes, it's on "sda1".
Yes, I have the original Live-CD.

[neerajkolte]

I'm using Puppy for some time; I think it happened gradually.
I hardly installed anything; so I have no idea how that happen.
Can it be some garbage; which I can remove?

Hi MrAccident, would something like this be of any interest to you. I searched forum with how to clean puppy and came up to this I haven't used it so don't know if it's what you need.

Then again I am new to linux, I might be wrong or interpreted your situation wrongly.
Hope this helps.

Thanks
- Neeraj

[Semme]

Previous post updated.

==

Boot your Pup cd to a live session with: puppy pfix=ram

After the desktop appears, open a shell and issue:

Code: Select all

e2fsck -f -n -v /dev/sda1

(f=force check, n=read-only check, v=verbose)

Depending on return code (0, 1 or 4), run the same, replacing -n with -p.

==

PS - I <NOT> love interruptions.

PSS - Humor me for a sec accident guy. The return here:

Code: Select all

ls -l /

If similar to mine >> you've got a problem!

[MrAccident]

Thanks neerajkolte; I'll try that later. I would like to understand this thing first. I don't like to just guess at stuff. Right now I hardly can understand how Linux works. Windows actually was much more straight forward. I guess that's what happens with an OS, which foundations are a geek made for geek OS. So for instance - I try to see what's in the partition where Puppy is, in GDmap; and don't see anything; and the whole thing with - folders are treated as if they are somewhere, even if you only have a link to them. I just can't understand how this whole think works.

[Galbi]

folders are treated as if they are somewhere, even if you only have a link to them. I just can't understand how this whole think works.

Perhaps because in Linux, everything it's a file.

Your modem, the hard disk/s, floppy disk, the printer, etc, etc. Everything it's a file.

For example if you look in /mnt maybe you can find two files sda1 and sda2 but if you look in those files (a folder it's speciall kind of file) there it's nothing inside. Why?, because the real hard disk exists but it's not mounted yet (the fact it's that file systems are mounted).
Once mounted, in /mnt/sda2 you can find other files/folders.

Another point that caused me confusion, were 'symlinks' symbolic links, the name might give you an idea of what they are. Shortly, you can symlink a folder of 1GB to anoter folder whithout duplicating the information. It's very usefull when an app needs to find something in an specific folder but it's really in another.

[MrAccident]

(f=force check, n=read-only check, v=verbose)

Depending on return code (0, 1 or 4), run the same, replacing -n with -p.

==

PS - I <NOT> love interruptions.

I didn't understand any of that; so I'll just paste all the results.

Code: Select all

# e2fsck -f -n -v /dev/sda1
e2fsck 1.42.6 (21-Sep-2012)
Warning: skipping journal recovery because doing a read-only filesystem check.
Superblock last mount time is in the future.
	(by less than a day, probably due to the hardware clock being incorrectly set)  Fix? no

Superblock last write time is in the future.
	(by less than a day, probably due to the hardware clock being incorrectly set).  Fix? no

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

      143370 inodes used (28.34%, out of 505920)
         206 non-contiguous files (0.1%)
          50 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 140581/38
     1922859 blocks used (95.08%, out of 2022400)
           0 bad blocks
           1 large file

      119209 regular files
       21314 directories
         170 character device files
         341 block device files
           0 fifos
           4 links
        2325 symbolic links (2230 fast symbolic links)
           2 sockets
------------
      143365 files

Code: Select all

# e2fsck -f -p -v /dev/sda1
/dev/sda1: recovering journal
/dev/sda1: Superblock last mount time is in the future.
	(by less than a day, probably due to the hardware clock being incorrectly set)  FIXED.

      143370 inodes used (28.34%, out of 505920)
         206 non-contiguous files (0.1%)
          50 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 140581/38
     1922859 blocks used (95.08%, out of 2022400)
           0 bad blocks
           1 large file

      119209 regular files
       21314 directories
         170 character device files
         341 block device files
           0 fifos
           4 links
        2325 symbolic links (2230 fast symbolic links)
           2 sockets
------------
      143365 files

Code: Select all

# ls -l /
total 0
drwxrwxrwx  2 root root   41 Nov 13  2013 archive
drwxr-xr-x  2 root root 2811 Mar  9 06:31 bin
drwxr-xr-x 17 root root 1340 May 27 18:35 dev
drwxr-xr-x 49 root root  560 May 27 18:36 etc
drwxr-xr-x 17 root root  360 May 28  2014 initrd
drwxr-xr-x 10 root root  100 May 28  2014 lib
drwxr-xr-x 11 root root  126 Nov 13  2013 mnt
drwxr-xr-x  2 root root    3 Mar  9 04:56 opt
dr-xr-xr-x 97 root root    0 May 28  2014 proc
drwxr-xr-x 29 root root  280 May 27 18:36 root
lrwxrwxrwx  1 root root    3 Nov 16  2013 run -> tmp
drwxr-xr-x  2 root root 3159 Mar  9 06:31 sbin
dr-xr-xr-x 12 root root    0 May 28  2014 sys
drwxrwxrwt 10 root root  960 May 27 18:36 tmp
drwxr-xr-x 21 root root  100 May 28  2014 usr
drwxrwxrwx 24 root root  180 May 27 18:35 var

[MrAccident]

Galbi - That doesn't help me understand it exactly.
I read about those links before; and I still don't understand the difference between absolute and relative; or what they are exactly; or how they work on NTFS. They seem to work as links, but...
I think that I couldn't see sda1 in GDmap, because that was where the OS was located; now from the live-CD - I can. Indeed I see things that aren't suppose to be there; like many things that I deleted; and weren't in that partition in the first place.

[Semme]

This one from your hd install, NOT the live system:

Code: Select all

ls -l /

With GdMap, the is to <hover over> blocks to disclose their size.

[MrAccident]

Code: Select all

# ls -l /
total 425184
-rw-r--r--  1 root root         0 Mar 24 13:54 1
drwxr-xr-x  2 root root      4096 May 15 00:41 audit
drwxr-xr-x  2 root root      4096 Mar  9 00:31 bin
drwxr-xr-x  4 root root      4096 Mar 30 10:48 boot
drwxr-xr-x 12 root root     13720 May 27 19:08 dev
drwxr-xr-x 45 root root      4096 May 27  2014 etc
-rw-rw-rw-  1 root root        10 May 27 19:08 fsckme.flg
-rw-r--r--  1 root root    220049 Apr 30 19:05 grldr
drwxr-xr-x  9 root root      4096 May  4 22:55 lib
-rw-r--r--  1 root root 169418752 Aug 10  2013 LibreOffice-4.1.0_en-US_xz.sfs
drwx------  2 root root      4096 Mar 26 12:22 lost+found
-rw-r--r--  1 root root       803 Mar 24 13:57 menu-2014-03-24-195701.lst
-rw-r--r--  1 root root       803 Mar 24 14:00 menu-2014-03-24-200051.lst
-rw-r--r--  1 root root       754 Mar 30 11:01 menu-2014-03-30-160122.lst
-rw-r--r--  1 root root       754 Apr 12 15:42 menu-2014-04-12-154252.lst
-rw-r--r--  1 root root       754 Apr 12 12:50 menu-2014-04-12-175012.lst
-rw-r--r--  1 root root       971 Apr 30 19:05 menu-advanced.lst
-rw-r--r--  1 root root       754 Apr 30 19:05 menu.lst
drwxr-xr-x 22 root root      4096 May 27  2014 mnt
-rw-r--r--  1 root root 135790592 Aug 10  2013 OpenOffice-4.0-x86-en_US-xz.sfs
drwxr-xr-x 15 root root      4096 May 15 03:05 opt
dr-xr-xr-x 96 root root         0 May 27  2014 proc
drwxr-xr-x 57 root root      4096 May 27 19:08 root
lrwxrwxrwx  1 root root         3 Nov 16  2013 run -> tmp
drwxr-xr-x  2 root root      4096 May 27  2014 sbin
-rw-r--r--  1 root root     32256 Mar 30 11:01 sda_mbr.bak
-rw-r--r--  1 root root     32256 Mar 24 13:57 sdb_mbr.bak
-rw-r--r--  1 root root 536870912 May 27  2014 slackosave.4fs
dr-xr-xr-x 12 root root         0 May 27  2014 sys
drwxrwxrwt 11 root root       700 May 27 19:38 tmp
drwxr-xr-x 19 root root      4096 May 14 22:15 usr
drwxr-xr-x 18 root root      4096 May  4 22:55 var