Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 05:14:34AM +0100, Tazman Deville wrote:
> On Mon, Nov 04, 2013 at 09:51:26PM -0600, Stan Hoeppner wrote:
> > On 11/4/2013 8:30 PM, Tazman Deville wrote:
> > > On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote:
> > >> Hi,
> > >>
> > >> Did you check inodes usage? (df -i)
> > >>
> > >> I could be inodes availability rather than block availability.
> > >
> > >
> > > AHA!
> > >
> > > df -i gives
> > > $ df -i
> > > Filesystem Inodes IUsed IFree IUse% Mounted on
> > > /dev/sda7 1729920 1729920 0 100% /
> > >
> >
> > First it means you're using a filesystem with a small fixed number of
> > inodes, obviously EXT.
> >
> > Second, you have a serious problem here because it is your root
> > filesystem that has run out of inodes. You need to ask yourself why you
> > have 1.7M files in your rootfs. That's very dumb. That's what /home
> > and /data and other places are to be used for.
>
> I'm not the dummy that filled up my /
> Before this, it was barely more than hafl full (well, df -h
> shows I'm only using 9.6gb of the 16gb there).
> Also, that hdd is old.
> I ran fedora core 4 on it.That's how old it is.
> Then I tried Ubuntu Dapper Duck on it, and some old PCLinuxOS,
> and eventually, when it was already about 3 years old,
> installed Lenny on it, my first Debian (and I'm still here!).
> But I formatted it as ext3 when I installed lenny,
> and from there just upgraded to squeeze with apt, so
> haven't changed the fs. Haven't had any reason to change it.
>
>
> So, anyway, after some digging around, I find there are some billions
> of log files in /var/log/ for popularity-contest.
>
> Like, this is 0.005% of the output of
> sudo find . -xdev -type f | cut -d "/" -f 2 | sort | uniq -c | sort -n
>
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1.1.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.2.gz
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.2.gz.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.2.gz
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1.1.1
> 1
> popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.2.gz
>
> I've aptitude purged popularity-contest, now.
> I checked the logrotate file, and it has a maxage of 7, meaning these
> are all a week old or younger, too.
> Very, very strange.
> Now I have to figure out how to get rid of them.
> Even trying to rm -rf a small subset, like *.1.2.gz.1.2.gz.1*
> gives me
> Argument list too long.
>
Got it!
find . -name 'popularity-*' | xargs rm -rf
(passes the files to rm one at a time).
The machine in question, btw, now simply sits quietly in a corner
of my office, serving up the scuttle, a little dokuwiki for my personal
use, and a couple of other useful things, sometimes serves as a sandbox
for trying stuff out before use on a production server.
It's a trooper, and, until today, has never given me any real problems.
My main box (one I'm typing on) runs Wheezy, with 4x2.8ghz AMD APU,
and 16gb ram, 2Tb storage, etc.
./taz
--
http://tazmandevil.info
taz hungry
Reply to: