I've updated the bug #1263. I am still periodically getting ENOSPC errors
out of this file system. Apparently bugzilla isn't accepting attachments at
this moment, so I'll attach the current stat_sysdir.sh output.
At this point, I can't continue having these errors in production. Next
week,
Unfortunately, we also have just started having the same issue and are
anxiously awaiting a solution. So far I've just deleted things I
didn't absolutely need in order to keep our production system running,
but that won't work forever.
The filesystem was defined for 750GB. We've currently got
On Fri, Jun 25, 2010 at 01:49:28PM -0400, Jason Price wrote:
I've updated the bug #1263. I am still periodically getting ENOSPC errors
out of this file system. Apparently bugzilla isn't accepting attachments at
this moment, so I'll attach the current stat_sysdir.sh output.
At this point, I
On Fri, Jun 25, 2010 at 02:03:59PM -0400, Eric Raskin wrote:
In the meantime, I'm planning on moving data off the file system,
re-creating it, then moving the data back on again. I'm hoping that
will defragment it enough to allow it to continue working for a while.
Does anyone know if I'm
Thanks very much. I'm not really sure about the difference between
mainline and production release. Are we looking at days, weeks, or
months? :-)
Eric
Joel Becker wrote:
On Fri, Jun 25, 2010 at 02:03:59PM -0400, Eric Raskin wrote:
In the meantime, I'm planning on moving data off the
'mainline' means 'the current release of the linux kernel' not 'patched down
into the distro level'.
I'm guessing here, but I think the 'production release' would mean OCFS2
v1.4.next.
--Jason
On Fri, Jun 25, 2010 at 3:12 PM, Eric Raskin eras...@paslists.com wrote:
Thanks very much. I'm not
(Sorry Tao: I realized I had just replied to you)
I just uploaded a third output from stat_sysfs.sh to bug # 1263. It was
taken while we were experiencing ENOSPC errors. In my limited testing, I
was able to write a 324k file, then a 1620k file (5x324), but failed to
write a 16200k file
Hi Jason,
On 06/09/2010 11:34 PM, Jason Price wrote:
And now it's starting to fail again.
How about the situation?
I checked your stat_sysfs output, it looks that you have spaces for
inode, extent alloc and local alloc(but maybe the kernel haven't flushed
the metadata to the disk while the
