linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Jingyun He <jingyun.ho@gmail.com>,
	linux-btrfs@vger.kernel.org, Naohiro Aota <Naohiro.Aota@wdc.com>,
	Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Subject: Re: seagate hm-smr issue
Date: Mon, 27 Sep 2021 08:13:22 +0900	[thread overview]
Message-ID: <b57cace4-fc85-2a5f-e88b-d056b12a2a0b@opensource.wdc.com> (raw)
In-Reply-To: <CAHQ7scUiLtcTqZOMMY5kbWUBOhGRwKo6J6wYPT5WY+C=cD49nQ@mail.gmail.com>

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

  reply	other threads:[~2021-09-26 23:13 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 [this message]
2021-09-26 23:42   ` Jingyun He
2021-09-27  0:07     ` Damien Le Moal
2021-12-27 17:46       ` Jingyun He

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=b57cace4-fc85-2a5f-e88b-d056b12a2a0b@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=Naohiro.Aota@wdc.com \
    --cc=jingyun.ho@gmail.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).