Linux Device Mapper development
 help / color / mirror / Atom feed
From: "monty_pavel@sina.com" <monty_pavel@sina.com>
To: dm-devel <dm-devel@redhat.com>
Cc: monty_pavel <monty_pavel@sina.com>
Subject: [dm-thin] problem about __shadow_block  function
Date: Mon, 26 Mar 2018 19:02:39 +0800	[thread overview]
Message-ID: <2018032619023829519519@sina.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 504 bytes --]

Hi all:
When I read __shadow_block  function, I found a problem as follows:
After called __shadow_block function, if the orig block is allocated to another and rewriten by another context, Meanwhile action mentioned above are committed in the same transaction, and then power loss happens before write superblock to metadata device. If the orig block is device_details_root of thin_disk_super_block, we can not find any device in thin-pool.
Is it possible?
Sincerely monty


monty_pavel@sina.com

[-- Attachment #1.2: Type: text/html, Size: 1285 bytes --]

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



                 reply	other threads:[~2018-03-26 11:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2018032619023829519519@sina.com \
    --to=monty_pavel@sina.com \
    --cc=dm-devel@redhat.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