linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 63511] EXT4-fs warning (device sdc): ext4_da_update_reserve_space:362: ino 75159523, allocated 1 with only 0 reserved metadata blocks (releasing 162 blocks with reserved 162 data blocks)
Date: Wed, 23 Oct 2013 10:40:00 +0000	[thread overview]
Message-ID: <bug-63511-13602-YenPqD3Rub@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-63511-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=63511

Jan Kara <jack@suse.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |jack@suse.cz
         Resolution|---                         |CODE_FIX

--- Comment #1 from Jan Kara <jack@suse.cz> ---
Thanks for report. This bug should be fixed by commit
7d7345322d60edb0fa49a64a89b31360f01d09cb (merged in 3.12-rc something). The
warning is mostly harmless though (the bug could lead to real problems only if
we hit ENOSPC condition).

I've asked stable kernel guys to take the commit into 3.10 and 3.11 -stable
series.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      reply	other threads:[~2013-10-23 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 17:38 [Bug 63511] New: EXT4-fs warning (device sdc): ext4_da_update_reserve_space:362: ino 75159523, allocated 1 with only 0 reserved metadata blocks (releasing 162 blocks with reserved 162 data blocks) bugzilla-daemon
2013-10-23 10:40 ` bugzilla-daemon [this message]

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=bug-63511-13602-YenPqD3Rub@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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).