On 17 April 2015 at 14:47, Chris Walker alug_cdw@the-walker-household.co.uk wrote:
In the root of the card might be a folder called $Recycle.Bin which, if it's there will contain the files.
Not there :-(
And in any case the more I think about this, if it were there then it would have shown in 'sudo du -h /' which it doesn't. Which is why William's suggestion to search for large files using "find" doesn't help either (I did try it, no files found). The file isn't "there" to find, however the space is still allocated.
If there's nothing important on the card, can you not format it?
It's the root filesystem of the device I'm SSH'ing into, so yes, it is important...
Where does "du" get it's information from? Are there any clues in the following? The "1 large file" sounds helpful but I can''t find any reference to what that means in practice. Note that fsck thinks I have 24% blocks used, which is about right, so why does "df" think I've used 74% of the disk?
Aside: I tried creating a large file to fill the disk (cp /dev/zero ~/tmpfile) and it exhausted available disk space at about 900M, agreeing with df.
$ sudo /sbin/fsck.ext3 -fnv /dev/sda2 e2fsck 1.42.5 (29-Jul-2012) 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
27366 inodes used (13.92%, out of 196608) 21 non-contiguous files (0.1%) 22 non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 1268/18/0 189248 blocks used (24.06%, out of 786432) 0 bad blocks 1 large file
22051 regular files 2444 directories 11 character device files 276 block device files 2 fifos 411 links 2572 symbolic links (2471 fast symbolic links) 1 socket $ df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 3756092 2638136 927156 74% / /dev/root 3756092 2638136 927156 74% / devtmpfs 256800 0 256800 0% /dev tmpfs 51376 212 51164 1% /run tmpfs 5120 0 5120 0% /run/lock tmpfs 102740 0 102740 0% /run/shm
Mark