What Is Using 1.5gb On Hdd3?

[Jon_J]

I know this topic has been discussed before, but I have searched and didn't find anything about a drive/partition that should be empty while using 1.5 GB of space.
I've enclosed a screenshot of Tree!explorer (with root priv enabled) and below is my output from console:

Code: [Select]

# df -h
Filesystem      Size   Used  Available  Use%   Mounted on
rootfs          32.0M  32.0M      0     100%   /
/dev/root       32.0M  32.0M      0     100%   /
/dev/ram1      108.0k  28.0k  80.0k      26%   /dev
/dev/loop0      25.9M  25.9M      0     100%   /dev
/dev/mtdblock3  89.0M  21.9M  67.1M      25%   /home
none            10.0M  32.0k  10.0M       0%   /dev/shm
/dev/hda1        9.5M   1.0M   8.0M      11%   /hdd1
/dev/hda2        9.5M   1.1M   7.9M      12%   /hdd2
/dev/hda3        3.8G   1.5G   2.3G      39%   /hdd3
What is using 1.5GB on this partition?
Look at the screenshot, and it shows the partition is "empty"
I deleted everything on it. Of course, I backed it up first.

Thank you
Jon

[iamasmith]

Maybe try...

cd /hdd3
du -h

and see what comes back...

[TRIsoft]

Jon_J,

are you sure that you removed the dictionary files and
directories in /hdd3/dict1 and /hdd3/dict2 ?

///TRIsoft

Marc Stephan

[Jon_J]

cd /hdd3
du -h
4.0k    .

It looks empty now, but why the confusing information with (df -h)?

Stephen, I removed those last week.
I'm wanting to add a ext2 partition. This is why I have deleted all the stuff on hdd3.

BTW, thanks for the 'cd' tip. I thought that was for changing directories only. (Old DOS habits are hard to shed).
Thank you,
Jon

[bluedevils]

I've seen this before on other *nix boxes.  df is not correct and I used to believe it was because a process was holding something open that was deleted (maybe the dictionary was on fast load).  Probably a reboot would fix things.  I'm not sure of another way.

[bluedevils]

BTW cd *is* change directories.  You could have carried out the command like this as well

du -h /hdd3

[Jon_J]

I rebooted, same result with df
If I deleted the dictionary files while they were set to "fast load", does that mean they are still using memory?

[daniel3000]

I rebooted, same result with df
If I deleted the dictionary files while they were set to "fast load", does that mean they are still using memory?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=112342\"][{POST_SNAPBACK}][/a][/div]

Well, maybe do a file system check. Maybe old data is deleted, but space has not been made available for new files.

If you boot with the B+D option, login as root and use
fsck.vfat -a -f -t -v -V /dev/hda3

daniel

[iamasmith]

To use the D+B option do as follows...

i. Remove power and battery from the SL-C3000.
ii. Leaving the Battery Cover OFF, return the battery cover lock to the LOCKED position.

At this point examine the battery compartment. On the edge that is closest to Zaurus Logo are a set of slots where the battery cover 'keys into' when closed.

If you look at the slot that sits almost exactly vertically central of the whole Zaurus (not the compartment) you will notice that there is a reset button. Do NOT press it just yet.

iii. Open the unit so the screen is at right angles to the base unit and sit the unit on the back of the screen so that the keyboard is accessible with one hand and the base of the unit is accessible with the other.

iv. Hold down D+B on the keyboard and whilst these keys are held depress the reset button using the stylus.

v. Release the D+B keys and within a few seconds the unit should start to boot into Emergency Linux.

You can now login as root with no password

[DReymann]

Hi,

I rebooted, same result with df
[...]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=112342\"][{POST_SNAPBACK}][/a][/div]

I am not totally shure but I have in mind that even on linux you have to delete the directory where the files were stored. Only then the inodes are back in the list of available inodes?

As I said, I am not totally shure, but may be worth a try.

Detlev

[daniel3000]

Hi,

I rebooted, same result with df
[...]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=112342\"][{POST_SNAPBACK}][/a][/div]

I am not totally shure but I have in mind that even on linux you have to delete the directory where the files were stored. Only then the inodes are back in the list of available inodes?

As I said, I am not totally shure, but may be worth a try.

Detlev
[div align=\"right\"][a href=\"index.php?act=findpost&pid=112352\"][{POST_SNAPBACK}][/a][/div]

That would be bad! <g>
Imagine a directory full of large files. You want to delete one large file to regain space on the drive. If you would have to delete the entire directory, you first had to move the other large files somewhere else.
I don't think that this can be the reason.

daniel

[Jon_J]

I rebooted and logged in as root using the B+D method
I used fsck.vfat -a -f -t -v -V /dev/hda3
It is checking for bad clusters now, but after about 5 minutes, the curser stopped blinking.
The battery light and disk light are both on. (I have it plugged into the power supply).
It's been awhile, and it still says "Checking for bad clusters"
How long should this take??

Thank you,
Jon

EDIT Whew, it's done. Any way to get a screenshot of the output?
This is what appeared after
Checking for bad clusters
-----------------------------------------------------------------
Reclaiming unconnected clusters.
Checking free cluster summery.
Free cluster summery wrong (608516 vs. really 992951)
Auto-correcting.
Starting verification pass.
Checking for unused clusters.
Performing changes.
/dev/hda3: 0 files, 1/992952 clusters
#
-----------------------------------------------------------------

[Jon_J]

Yeah! I think I got it. I hope there aren't any other issues though..

Code: [Select]

$ df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                   32.0M     32.0M         0 100% /
/dev/root                32.0M     32.0M         0 100% /
/dev/ram1               108.0k     28.0k     80.0k  26% /dev
/dev/loop0               25.9M     25.9M         0 100% /usr
/dev/mtdblock3           89.0M     22.0M     67.0M  25% /home
none                     10.0M     24.0k     10.0M   0% /dev/shm
/dev/mmcda1             968.3M    333.4M    634.8M  34% /usr/mnt.rom/card
/dev/hda1                 9.5M      1.0M      8.0M  11% /hdd1
/dev/hda2                 9.5M      1.1M      7.9M  12% /hdd2
/dev/hda3                 3.8G      4.0k      3.8G   0% /hdd3

[bluedevils]

BTW were you in the directory you were deleting while you were deleting it?

[Jon_J]

If you mean while I deleted all the sharp stuff and dictionaries, I first deleted the individual files within the directories, then when all the directories were empty, I was in /hdd3, then I deleted each empty directory, individually.
I used Tree!explorer to delete the files & directories.

Thank you for your help bluedevils,
Jon