linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jehan procaccia <jehan.procaccia@it-sudparis.eu>
To: linux-ext4@vger.kernel.org
Subject: ext4 and quota generate "Data will be lost" errors :-(
Date: Thu, 17 Sep 2009 15:49:52 +0200	[thread overview]
Message-ID: <4AB23E80.9070805@it-sudparis.eu> (raw)

Since I run a ext4 FS with quota on my Redhat 5.4 , I often get these 
kind of messages on the console:

Message from syslogd@ at Thu Sep 17 15:40:11 2009 ...
gizeh kernel: mpage_da_map_blocks block allocation failed for inode 
3412191 at logical offset 0 with max blocks 1 with error -122
Message from syslogd@ at Thu Sep 17 15:40:11 2009 ...
gizeh kernel: This should not happen.!! Data will be lost

my system is runing on:
$ uname -a
Linux gizeh.int-evry.fr 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 
2009 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -q quota
quota-3.16-7 
I upgraded redhat quota package from recompile fedora10 sources because 
of this changelog:

* Thu Oct 30 2008 Ondrej Vasik <ovasik@redhat.com <mailto:ovasik@redhat.com>> 1:3.16-6
- fix implementation of ext4 support


I have a discussion with redhat on this: 
https://bugzilla.redhat.com/show_bug.cgi?id=522615
the reponse is to move back to ext3 until redhat support quota for ext4 .

my probleme is that I have lot of users and filesystems in this 
situation now, and I wonder I couldn't expect a workaround ?
is this issue know in recent kernel,  will I really lose data ? 
any advice greatly appreciated .

regards



             reply	other threads:[~2009-09-17 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 13:49 jehan procaccia [this message]
2009-09-17 14:40 ` ext4 and quota generate "Data will be lost" errors :-( Eric Sandeen
2009-09-17 15:53   ` jehan procaccia
2009-09-17 15:58     ` Eric Sandeen

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=4AB23E80.9070805@it-sudparis.eu \
    --to=jehan.procaccia@it-sudparis.eu \
    --cc=linux-ext4@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).