Comments on: df and zettabytes

By: ward

ward — Fri, 03 Jul 2009 13:52:47 +0000

Yeah, fixing this is obviously on my todo list. But like I said, this is just a dom0 filesystem on one system in a cluster, and the domUs are in lvm slices. The domUs are important; the dom0 as such is not very important.

By: wo.uter.be/

wo.uter.be/ — Fri, 03 Jul 2009 13:30:11 +0000

This kind of thing usually points to corruption.

If I were you, I’d take the filesystem offline immediately, and run ‘fsck -f’. If that finds nothing, no worries — but better safe than sorry.

It’s quite unlikely that this is related to sparse files. Really.

By: ward

ward — Sun, 28 Jun 2009 14:59:23 +0000

Well, there’s nothing special in mount or fdisk -l.

/dev/md0 on / type ext3 (rw,errors=remount-ro)

It may be caused by sparse files. This is a xen dom0 that was used for some iscsi experimentation a while back and this may be a result of that. But I don’t know exactly what the person doing the iscsi testing did, so it’s hard to say.

It’s an old 2.6.18-xen kernel. But I have loads of those running still, and this is the only box I’m seeing this on. The machine’s been up for a long time – 607 days currently. This is a production machine, and du -sh is normal:

# du -sh
8.5G	.

So I’m not too worried.

By: emailtoid.net/i/eca7e350/…

emailtoid.net/i/eca7e350/… — Tue, 23 Jun 2009 10:06:42 +0000

It would be intersting to see some more:
fdisk -l
mount
…

What is causing this ? Sparse files ?