From: Massimo Cetra <ctrixk@navynet.it>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] disk full when it shouldn't
Date: Mon, 08 Nov 2010 16:14:27 +0100 [thread overview]
Message-ID: <4CD813D3.4080106@navynet.it> (raw)
Hi all,
i've been using OCFS2 for a while (2 years or so, now) but i still have
a big problem.
on each filesystem that i have, it happens that, even if df reports that
the disk has plenty of free space avalaible, no one can write any file.
This behaviour has happened for several usages of OCFS2 (webserver and
mail storage) so both with big files and small files.
It happens more frequently on the mail partitions that i manage.
I have tried to search for some documentation about this problems and it
seems that i'm not the only one experiencing this behaviour.
The kernels showing this behaviour are both 2.6.32 and 2.6.31.
This happens with OCFS2-tools 1.4.2 and 1.4.3
In the last weeks i have reformatted some partitions from scratch using
1.4.3 but the problem persists.
I have found somewhere a bash script to analyze the sysdir and output
useful informations for the debugging.
The output of this script during the problem is attached.
Any hint about this ?
Thanks,
Max
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: debugfs.txt
Url: http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20101108/6a59bcae/attachment-0001.txt
next reply other threads:[~2010-11-08 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 15:14 Massimo Cetra [this message]
2010-11-09 1:06 ` [Ocfs2-devel] disk full when it shouldn't Tao Ma
2010-12-02 17:20 ` Massimo Cetra
2010-12-03 1:22 ` Tao Ma
2010-12-03 2:16 ` Tao Ma
2010-12-27 14:31 ` Massimo Cetra
2010-12-27 15:48 ` Tao Ma
2010-12-27 16:52 ` Sunil Mushran
2010-12-28 11:38 ` Massimo Cetra
2010-12-28 12:06 ` Massimo Cetra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CD813D3.4080106@navynet.it \
--to=ctrixk@navynet.it \
--cc=ocfs2-devel@oss.oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.