All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Black <dankamongmen@gmail.com>
To: Shaohua Li <shli@kernel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: data loss+inode recovery using RAID6 write journal
Date: Wed, 26 Oct 2016 14:51:33 -0400	[thread overview]
Message-ID: <20161026185133.thjrnsrtzlagegen@schwarzgerat.orthanc> (raw)
In-Reply-To: <20161026184359.u7pwbxzz7i5mcbfm@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]

Shaohua Li left as an exercise for the reader:
> Thanks for the testing. We can't improve the quality of the new feature if
> nobody tests it. Yep, the write journal isn't mature yet, but I can't imagine
> the data loss. With write journal, data is written to the ssd first, then to
> raid disks and IO is finished at that time. So if IO is finished, the data
> should be in raid disks. The only possible way to data loss is the recovery.
> But it's also possible filesystem/writeback hasn't flushed data to disk yet.
> I'm wondering if you can reproduce it with/without journal, so we can narrow
> down it a bit.

I doubt it can be replaced without the journal -- like I said, I've been
using mdadm RAID[56] for over a decade, and never seen such a problem.

I'll attempt to reproduce with the journal enabled. Assuming I can, I can
try to reproduce without, but I doubt it'll be fruitful. Are there any
debugging options / flags I should enable prior reproducing in order to get
a more complete report? Some state I should dump from my array and
filesystems? Feel free to be technical.

I owe a lot to Linux MD RAID, and am happy to put some effort into running
this down.

I'll report whether I can at least reproduce ASAP.

--nick

-- 
nick black -=- http://www.nick-black.com
to make an apple pie from scratch, you need first invent a universe.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

      reply	other threads:[~2016-10-26 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 23:55 data loss+inode recovery using RAID6 write journal Nick Black
2016-10-25 12:36 ` Wols Lists
2016-10-25 13:16   ` Nick Black
2016-10-26 18:43 ` Shaohua Li
2016-10-26 18:51   ` Nick Black [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=20161026185133.thjrnsrtzlagegen@schwarzgerat.orthanc \
    --to=dankamongmen@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=shli@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 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.