From: Jingyun He <jingyun.ho@gmail.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: linux-btrfs@vger.kernel.org, Naohiro Aota <Naohiro.Aota@wdc.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Subject: Re: seagate hm-smr issue
Date: Tue, 28 Dec 2021 01:46:49 +0800 [thread overview]
Message-ID: <CAHQ7scX1dc3LtT5-Ms+AvPwTBkKvi4017_Lnd-N7kBR7PGUvcg@mail.gmail.com> (raw)
In-Reply-To: <54911068-8a81-4201-bf1f-e8dcd196bb08@opensource.wdc.com>
Hello,
Do you have any update on this? or any patch that I can try?
Thanks.
On Mon, Sep 27, 2021 at 8:07 AM Damien Le Moal
<damien.lemoal@opensource.wdc.com> wrote:
>
> On 2021/09/27 8:42, Jingyun He wrote:
> > Hi,
> > You are correct, for a WD/HGST HM-SMR disk, it takes about 15 mins to
> > mount a full disk.
> >
> > But It takes about 2-3 hours for mounting a Seagate HM-SMR disk.
> >
> > Have no idea why Seagate takes so loooooong time.
>
> This is most likely due to a difference in the execution time of report zones
> commands.
>
> In any case, this will be resolved soon as we can cache a full disk zone report
> during the mount operation to avoid this slow per-zone report operation.
>
> >
> > On Mon, Sep 27, 2021 at 7:13 AM Damien Le Moal
> > <damien.lemoal@opensource.wdc.com> wrote:
> >>
> >> On 2021/09/26 22:57, Jingyun He wrote:
> >>> Hello,
> >>> Btrfs works very well on WD/HGST disks, we got some Seagate HM-SMR
> >>> disks recently, model number is ST14000NM0428,
> >>> mkfs.btrfs works fine, and I can mount it, and push data into disk.
> >>> once we used up the capacity, and umount it. then we are unable to
> >>> re-mount it again.
> >>> The mount process will never end, the process just hangs there.
> >>>
> >>> Anybody can help me with this?
> >>
> >> +Naohiro and Johannes
> >>
> >> This is not a hang. Mount will just take a looooong time due to an inefficiency
> >> in how block groups are checked: a single zone report zone command is issued per
> >> block group, so with a disk almost full, that takes a long time (75000+zones
> >> checked one by one). Naohiro is working on a fix for this.
> >>
> >>>
> >>> Thanks.
> >>>
> >>
> >>
> >> --
> >> Damien Le Moal
> >> Western Digital Research
>
>
> --
> Damien Le Moal
> Western Digital Research
prev parent reply other threads:[~2021-12-27 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 13:57 seagate hm-smr issue Jingyun He
2021-09-26 23:13 ` Damien Le Moal
2021-09-26 23:42 ` Jingyun He
2021-09-27 0:07 ` Damien Le Moal
2021-12-27 17:46 ` Jingyun He [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=CAHQ7scX1dc3LtT5-Ms+AvPwTBkKvi4017_Lnd-N7kBR7PGUvcg@mail.gmail.com \
--to=jingyun.ho@gmail.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-btrfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).