[Ocfs2-users] No space left on device

[Brad Plant]

On Wed, 16 Dec 2009 16:31:22 -0800
Sunil Mushran <sunil.mushran at oracle.com> wrote:

> Brad Plant wrote:
> > I have this happen on different file systems running different mainline kernel versions created with different versions of ocfs2-tools. I've seen 1 file system "fill up" with only 40% odd in use according to df. What's interesting is that while 1 node can't write anymore, another node (only 2 nodes mounted rw) will still be able to write to the FS, but neither will be able to completely fill the FS.
> >
> > I have created new ocfs2 file systems and the problem doesn't seem to occur (or it gets very close be actually being full), but weeks/months later after being in use, the problem develops. The FS I mentioned above that filled up at ~40% use was about 6 months old and you could say it did it's fair share of "work".
> >
> > I just dumped some 1GB files in a directory using dd to fill up a FS (full at 87%) to that I could collect some debugfs.ocfs2 information. Upon not being able to create any further 1GB files (operations on the FS got really slow), I successfully created some 10MB files. I then created 100+ 1MB files using dd. What seemed strange is that dd kept returning "no space left on device", but it would always write 995328 bytes of data to the file.
> >
> > dd if=/dev/zero of=2156 bs=1k count=1k
> > dd: writing `2156': No space left on device
> > 973+0 records in
> > 972+0 records out
> > 995328 bytes (995 kB) copied, 0.0551648 s, 18.0 MB/s
> >
> > dd if=/dev/zero of=2157 bs=1k count=1k
> > dd: writing `2157': No space left on device
> > 973+0 records in
> > 972+0 records out
> > 995328 bytes (995 kB) copied, 0.0545104 s, 18.3 MB/s
> 
> This looks like bz#1189.
> http://oss.oracle.com/bugzilla/show_bug.cgi?id=1189
> 
> We are working on the fix. The patch is in review.
> http://oss.oracle.com/osswiki/OCFS2/SmallTasksList
> 
> If all goes well, the next release will have the fix.

Thanks for the reply Sunil. I read through the 2 links you provided, but I have a question. The info mentioned modifications to mkfs to pre-allocate some area for extent stuff. Does this mean that we would have to create a new FS to fix the problem or will there also be a fix in the kernel that allows files to be moved on-disk to create some contiguous free space?

Cheers,

Brad