All of lore.kernel.org
 help / color / mirror / Atom feed
From: wangyf <wangyf-fnst@cn.fujitsu.com>
To: Ed Tomlinson <edt@aei.ca>, Omar Sandoval <osandov@fb.com>
Cc: <linux-btrfs@vger.kernel.org>, Miao Xie <miaoxie@huawei.com>,
	Zhao Lei <zhaolei@cn.fujitsu.com>,
	Philip <bugzilla@philip-seeger.de>
Subject: Re: [PATCH v2 0/5] Btrfs: RAID 5/6 missing device scrub+replace
Date: Thu, 25 Jun 2015 13:03:57 +0800	[thread overview]
Message-ID: <558B8BBD.2010004@cn.fujitsu.com> (raw)
In-Reply-To: <5cfdd3e8-e9ba-4b3a-a858-49f6a36f18de@aei.ca>

  I confirmed this bug report, and found the reason is that
  I compiled the patched module with a dirty kernel.
  This morning I tested this patch again, and didn't see above error, 
this patch is OK.
  Sorry for this bug report. : (


在 2015年06月24日 20:00, Ed Tomlinson 写道:
> On Wednesday, June 24, 2015 12:15:29 AM EDT, Omar Sandoval wrote:
>> On Tue, Jun 23, 2015 at 11:07:00AM +0800, wangyf wrote:
>>> Hi,
>>> I have tested your PATCH v2 , but something wrong happened.
>>>
>>> kernel: 4.1.0-rc7+ with your five patches
>>> vitrualBox ubuntu14.10-server + LVM
>>>
>>> I make a new btrfs.ko with your patches,
>>> rmmod original module and insmod the new.
>>>
>>> When I use the profile RAID1/10, mkfs successfully
>>> But when mount the fs, dmesg dumped:
>>>     trans: 18446612133975020584 running 5
>>>     btrfs transid mismatch buffer 29507584, found 18446612133975020584
>>> running 5
>>>     btrfs transid mismatch buffer 29507584, found 18446612133975020584
>>> running 5
>>>     btrfs transid mismatch buffer 29507584, found 18446612133975020584
>>> running 5
>>> ... ...
>>>
>>> When use the RAID5/6, mkfs and mount
>>> system stoped at the 'mount -t btrfs /dev/mapper/server-dev1 /mnt' cmd.
>>>
>>> That's all.
>>
>> Hm, that's really weird, I can't reproduce that here at all. I don't see
>> what would cause that in this series, and the changes from v1 are
>> minimal. For my sake, could you make sure that there's nothing else
>> going on?
>
> Omar,
>
> I've been running v1 of this patch and now with v2 and have done 
> numberious reboots without issues...  Just another data point.
>
> Ed


  reply	other threads:[~2015-06-25  5:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 18:52 [PATCH v2 0/5] Btrfs: RAID 5/6 missing device scrub+replace Omar Sandoval
2015-06-19 18:52 ` [PATCH v2 1/5] Btrfs: remove misleading handling of missing device scrub Omar Sandoval
2015-06-19 18:52 ` [PATCH v2 2/5] Btrfs: count devices correctly in readahead during RAID 5/6 replace Omar Sandoval
2015-06-19 18:52 ` [PATCH v2 3/5] Btrfs: add RAID 5/6 BTRFS_RBIO_REBUILD_MISSING operation Omar Sandoval
2015-06-19 18:52 ` [PATCH v2 4/5] Btrfs: fix device replace of a missing RAID 5/6 device Omar Sandoval
2015-06-19 18:52 ` [PATCH v2 5/5] Btrfs: fix parity scrub of RAID 5/6 with missing device Omar Sandoval
2015-06-23  3:07 ` [PATCH v2 0/5] Btrfs: RAID 5/6 missing device scrub+replace wangyf
2015-06-24  4:15   ` Omar Sandoval
2015-06-24 12:00     ` Ed Tomlinson
2015-06-25  5:03       ` wangyf [this message]
2015-06-25 16:35         ` Omar Sandoval
2015-06-26  2:07           ` wangyf
2015-06-26  2:46           ` wangyf

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=558B8BBD.2010004@cn.fujitsu.com \
    --to=wangyf-fnst@cn.fujitsu.com \
    --cc=bugzilla@philip-seeger.de \
    --cc=edt@aei.ca \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=osandov@fb.com \
    --cc=zhaolei@cn.fujitsu.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 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.