public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com, aelder@sgi.com
Subject: Re: Slow delete
Date: Tue, 20 Jul 2010 13:04:28 +0200	[thread overview]
Message-ID: <201007201304.28490@zmi.at> (raw)
In-Reply-To: <1279565697.1855.136.camel@doink>


[-- Attachment #1.1: Type: Text/Plain, Size: 1305 bytes --]

On Montag, 19. Juli 2010 Alex Elder wrote:
> Assuming your single head is still in good enough shape
> to understand this, here's a high-level (though imprecise)
> explanation.
 
Thank you Alex for the summary, but that was the part I understood. I 
didn't understand the in-depth explanation later, where XFS internals 
were described. But I guess it's not something I must understand. The 
short summary is: XFS will be faster, but really shouldn't crash when 
using delayed logging.

It will be interesting to see what happens on a busy system during a 
crash. Deleted files will appear again, some file changes won't be 
committed, and again the big problem: some config files might be gone as 
the rename/recreate transaction will not be done safe via fsync, and 
people will cry. The plus in performance might be worth it.

Can someone guess the exact problems that can happen with delayed 
transaction on a crash?

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-07-20 11:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinPmhJRD3CDdsHtkLFzYd2jF9ee7gPqgO6XBSfl@mail.gmail.com>
2010-07-05 15:13 ` Slow delete Emmanuel Florac
2010-07-05 15:33   ` Andrei Deftu
2010-07-05 18:21     ` Peter Grandi
2010-07-05 18:54   ` Christoph Hellwig
2010-07-05 23:34 ` Dave Chinner
2010-07-12 12:17   ` Michael Monnerie
2010-07-19 18:54     ` Alex Elder
2010-07-20 11:04       ` Michael Monnerie [this message]
2010-07-20 17:09         ` Stan Hoeppner
2010-07-20 23:18         ` Dave Chinner

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=201007201304.28490@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=aelder@sgi.com \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox