Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH DRAFT] btrfs: RAID56J journal on-disk format draft
Date: Wed, 01 Jun 2022 17:07:42 +0800	[thread overview]
Message-ID: <20220601170741.4B12.409509F4@e16-tech.com> (raw)
In-Reply-To: <49fb1216-189d-8801-d134-596284f62f1f@gmx.com>

Hi,

> On 2022/6/1 10:25, Wang Yugui wrote:
> > Hi,
> >
> >> On 2022/6/1 10:06, Wang Yugui wrote:
> >>> Hi,
> >>>
> >>>> This is the draft version of the on-disk format for RAID56J journal.
> >>>>
> >>>> The overall idea is, we have the following elements:
> >>>>
> >>>> 1) A fixed header
> >>>>      Recording things like if the journal is clean or dirty, and how many
> >>>>      entries it has.
> >>>>
> >>>> 2) One or at most 127 entries
> >>>>      Each entry will point to a range of data in the per-device reserved
> >>>>      range.
> >>>
> >>> Can we put this journal in a device just like 'mke2fs -O journal_dev'
> >>> or 'mkfs.xfs -l logdev'?
> >>>
> >>> A fast & small journal device may help the performance.
> >>
> >> Then that lacks the ability to lose one device.
> >>
> >> The journal device must be there no matter what.
> >>
> >> Furthermore, this will still need a on-disk format change for a special type of device.
> >
> > If we save journal on every RAID56 HDD, it will always be very slow,
> > because journal data is in a different place than normal data, so HDD
> > seek is always happen?
> >
> > If we save journal on a device just like 'mke2fs -O journal_dev' or 'mkfs.xfs
> > -l logdev', then this device just works like NVDIMM?  We may not need
> > RAID56/RAID1 for journal data.
> 
> That device is the single point of failure. You lost that device, write
> hole come again.

The HW RAID card have 'single point of failure'  too, such as the NVDIMM
inside HW RAID card. 

but  power-lost frequency > hdd failure frequency  > NVDIMM/ssd failure
frequency

so It still help a lot.

> RAID56 can tolerant one or two device failures for sure.
> Thus one point failure is against RAID56.
> 
> 
> If one is not bothered with writehole, then they doesn't need any
> journal at all.

I though 'degraded read-only' will help more case than 'degraded
read-write' with writehole.

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2022/06/01



  reply	other threads:[~2022-06-01  9:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  6:13 [PATCH DRAFT] btrfs: RAID56J journal on-disk format draft Qu Wenruo
2022-05-24 11:08 ` kernel test robot
2022-05-24 12:19 ` kernel test robot
2022-05-24 17:02 ` David Sterba
2022-05-24 22:31   ` Qu Wenruo
2022-05-25  9:00   ` Christoph Hellwig
2022-05-25  9:13     ` Qu Wenruo
2022-05-25  9:26       ` Christoph Hellwig
2022-05-25  9:35         ` Qu Wenruo
2022-05-26  9:06           ` waxhead
2022-05-26  9:26             ` Qu Wenruo
2022-05-26 15:30               ` Goffredo Baroncelli
2022-05-26 16:10                 ` David Sterba
2022-06-01  2:06 ` Wang Yugui
2022-06-01  2:13   ` Qu Wenruo
2022-06-01  2:25     ` Wang Yugui
2022-06-01  2:55       ` Qu Wenruo
2022-06-01  9:07         ` Wang Yugui [this message]
2022-06-01  9:27           ` Qu Wenruo
2022-06-01  9:56             ` Paul Jones
2022-06-01 10:12               ` Qu Wenruo
2022-06-01 18:49                 ` Martin Raiber
2022-06-01 21:37                   ` Qu Wenruo
2022-06-03  9:32                     ` Lukas Straub
2022-06-03  9:59                       ` Qu Wenruo
2022-06-06  8:16                         ` Qu Wenruo
2022-06-06 11:21                           ` Qu Wenruo
2022-06-06 18:10                             ` Goffredo Baroncelli
2022-06-07  1:27                               ` Qu Wenruo
2022-06-07 17:36                                 ` Goffredo Baroncelli
2022-06-07 22:14                                   ` Qu Wenruo
2022-06-08 17:26                                     ` Goffredo Baroncelli
2022-06-13  2:27                                       ` Qu Wenruo
2022-06-08 15:17                         ` Lukas Straub
2022-06-08 17:32                           ` Goffredo Baroncelli
2022-06-01 12:21               ` Qu Wenruo
2022-06-01 14:55                 ` Robert Krig

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=20220601170741.4B12.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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