To help in troubleshooting, use a tool that tells you where the drive space is being spent: You can use to get an overview of where space is going.

Even better, use a graphical tool like xdiskusage (there are many like this) to hunt down the culprit.

Per pehrs, lsof L1 is probably the better way to go.

as Ignacio mentions, deleting the file won't free the space until you delete the processes that have open handles against that file.

First execute lsof | grep deleted to identify the process holding the file One possibility is that the file(s) you deleted have more references in the filesystem.

If you've created hardlinks, several filenames will point to the same data, and the data (the actual contents) won't be marked as free/usable until all references to it has been removed.

xdiskusage and friends let you drill down into the biggest space hogs to find where space is going.

That way, you'll quickly find files that still occupy space because of a second hardlink.

Cc: Willem de Bruijn --- drivers/net/virtio_net.c | 47 ---------------- 1 file changed, 31 insertions( ), 16 deletions(-) diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c index 11e2853..05a83db 100644 --- a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c @@ -719,13 719,13 @@ static struct sk_buff *receive_mergeable(struct net_device *dev, return NULL; } -static void receive_buf(struct virtnet_info *vi, struct receive_queue *rq, - void *buf, unsigned int len) static int receive_buf(struct virtnet_info *vi, struct receive_queue *rq, void *buf, unsigned int len) if (vi-mergeable_rx_bufs) @@ -750,14 750,11 @@ static void receive_buf(struct virtnet_info *vi, struct receive_queue *rq, skb = receive_small(dev, vi, rq, buf, len); if (unlikely(!

int stat(const char *path, struct stat *buf); int fstat(int fd, struct stat *buf); int lstat(const char *path, struct stat *buf); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): These functions return information about a file.

lstat() is identical to stat(), except that if path is a symbolic link, then the link itself is stat-ed, not the file that it refers to.