Linux EXT4 FS development
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 71791] Unlinking a file that was moved to another folder but still open by other process blocks either process (not always reproducible)
Date: Tue, 11 Mar 2014 20:14:17 +0000	[thread overview]
Message-ID: <bug-71791-13602-4LFzENGHK3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71791-13602@https.bugzilla.kernel.org/>

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

Jan Kara <jack@suse.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |jack@suse.cz

--- Comment #1 from Jan Kara <jack@suse.cz> ---
So one note is that we are likely waiting for writeback on some page in that
file to finish. Another note is that I don't think another process has the file
open - the stacktrace clearly shows that we are completely deleting the file
which means noone can have the file open (if you can really show otherwise, it
would be a major bug).

I guess the file has been written quite recently and the filesystem is quite
loaded with the IO, isn't it?

Can you try mounting the filesystem with 'noauto_da_alloc' mount option?

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

  reply	other threads:[~2014-03-11 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 14:01 [Bug 71791] New: Unlinking a file that was moved to another folder but still open by other process blocks either process (not always reproducible) bugzilla-daemon
2014-03-11 20:14 ` bugzilla-daemon [this message]
2014-03-16  7:20 ` [Bug 71791] " bugzilla-daemon
2014-03-18 15:35 ` bugzilla-daemon

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-71791-13602-4LFzENGHK3@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