From: "hch@lst.de" <hch@lst.de>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"axboe@fb.com" <axboe@fb.com>,
"Sangaraju, Someswarudu" <ssomesh@amazon.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"Singh, Balbir" <sblbir@amazon.com>, "hch@lst.de" <hch@lst.de>
Subject: Re: [RFC][PATCH] nvme/core: Notify udev about capacity change
Date: Tue, 3 Dec 2019 13:52:23 +0100 [thread overview]
Message-ID: <20191203125223.GA29831@lst.de> (raw)
In-Reply-To: <20191203124351.GE21721@Johanness-MacBook-Pro.local>
On Tue, Dec 03, 2019 at 01:43:51PM +0100, Johannes Thumshirn wrote:
> I had this on my TODO List but one thing stopped my endeavors, having a
> "notifier" for resize is easy when we only grow the block-device, but what
> should the FS do when we shrink it?
Assuming this is a "normal" fs and not something fancy with built
in redundancy - shut the file system down and stop any new access to
it as that would just make things worse.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-12-03 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 0:27 [RFC][PATCH] nvme/core: Notify udev about capacity change Balbir Singh
2019-11-29 8:24 ` Christoph Hellwig
2019-12-02 23:35 ` Singh, Balbir
2019-12-03 6:54 ` hch
2019-12-03 7:26 ` Chaitanya Kulkarni
2019-12-03 7:34 ` hch
2019-12-03 12:43 ` Johannes Thumshirn
2019-12-03 12:52 ` hch [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=20191203125223.GA29831@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=axboe@fb.com \
--cc=jthumshirn@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sblbir@amazon.com \
--cc=ssomesh@amazon.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;
as well as URLs for NNTP newsgroup(s).