Forum

Hi.

I´m a new user of Xbian.

I have a problem with the available space on my SD.
Only 400 Mb free of 8 Gb.

only xbian with some widgets and skins and sickrage. ¿this is normal occuped space?

I executed three commands:

du -h / | grep ^[0-9].K >filesKb.txt
du -h / | grep ^[0-9].M >filesMb.txt
du -h / | grep ^[0-9].G >filesGb.txt

the addition of sizes of every line in three files is much lower than 4 Gb, but when I do a
df -h / the result is:

Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 7.2G 6.5G 424M 94% /

Where are the other 3Gb ? How can I see where is my lost space?

thanks in advance.

Quote:Where are the other 3Gb ? How can I see where is my lost space?

Probably in snapshots. You can manage those snapshots by cmdline program btrfs-auto-snapshot

See also here

Removing all snapshot with:
sudo btrfs-auto-snapshot list | grep -v /@$ | grep auto-snap | xargs -L1 sudo btrfs-auto-snapshot destroy

have recovered no more than 200Mb

/dev/mmcblk0p2 7.2G 6.5G 624M 92% /

Hmmm, please show me the output of sudo btrfs filesystem df /


That's my output of a 2.5 year old rpi1 installation (7.2G root partition)

and sudo du -d 1 -h --exclude="/proc" --exclude="/sys" --exclude="/dev" /
could be helpful

I would check your sickrage folders as these have a habit of filling up.

If that doesn't help, try installing the "tree" command as this should pinpoint where the usage is.

(30th Mar, 2016 02:31 AM)Nachteule Wrote: [ -> ]Hmmm, please show me the output of sudo btrfs filesystem df /

(30th Mar, 2016 02:31 AM)Nachteule Wrote: [ -> ]and sudo du -d 1 -h --exclude="/proc" --exclude="/sys" --exclude="/dev" /

Thanks !!

(30th Mar, 2016 04:00 AM)IriDium Wrote: [ -> ]I would check your sickrage folders as these have a habit of filling up.

If that doesn't help, try installing the "tree" command as this should pinpoint where the usage is.

I´ve installed the tree command.
In a global view, there is not files with big size... a lot with size of Kb, and a few with some Mb´s.

df output looks ok (/media has 1.1T so I suppose there was an external disk attached), so I see two possible reasons:

1. you have still one or more snapshots which consumes all the space
-> delete all subvolumes expect */@ (at least you did not delete the last_good_known snaps)
2. your FS is corrupt
-> fastest possible solution: make image from your current sys and reflash card again (see here)

(31st Mar, 2016 10:10 PM)Nachteule Wrote: [ -> ]df output looks ok (/media has 1.1T so I suppose there was an external disk attached), so I see two possible reasons:

1. you have still one or more snapshots which consumes all the space
-> delete all subvolumes expect */@ (at least you did not delete the last_good_known snaps)
2. your FS is corrupt
-> fastest possible solution: make image from your current sys and reflash card again (see here)

I´ll try.
Thanks !!!!

Very strange. Might be worth removing the widgets and add-ons - some skins can have a fairly high usage - but not that much. It might pinpoint the issue.

The other option (If nothing sensitive is contained within it) is to create and image using xbian-config copy function and post this image somewhere, where we can download and install it - to see what is causing the issue.

(1st Apr, 2016 03:27 AM)IriDium Wrote: [ -> ]The other option (If nothing sensitive is contained within it) is to create and image using xbian-config copy function and post this image somewhere, where we can download and install it - to see what is causing the issue.

Good idea, but would not help us finding the culprit, because xbian-config generates a completely new FS during backing up image

@Nachteule In that case a RAW image would help - Win32diskimager or Ubuntu Disk would give an image we could play with.

I'm intrigued as to what the issue is and would like to solve it, for my own curiosity. I don't believe it's an xbian issue but it puzzles me

At least it would be very interesting investigating this raw image