From: Andreas Dilger <adilger@dilger.ca> To: John Spray <john.spray@redhat.com> Cc: "Jan Kara" <jack@suse.cz>, "Austin S Hemmelgarn" <ahferroin7@gmail.com>, "Beata Michalska" <b.michalska@samsung.com>, LKML <linux-kernel@vger.kernel.org>, "Theodore Ts'o" <tytso@mit.edu>, "Hugh Dickins" <hughd@google.com>, "Lukáš Czerner" <lczerner@redhat.com>, "Christoph Hellwig" <hch@infradead.org>, Ext4 <linux-ext4@vger.kernel.org>, linux-mm <linux-mm@kvack.org>, kyungmin.park@samsung.com, kmpark@infradead.org, "Linux Filesystem Mailing List" <linux-fsdevel@vger.kernel.org>, "Linux API" <linux-api@vger.kernel.org> Subject: Re: [RFC 1/4] fs: Add generic file system event notifications Date: Fri, 17 Apr 2015 16:37:32 -0600 [thread overview] Message-ID: <A8EE2778-45FE-4EC6-AB41-278D8745D068@dilger.ca> (raw) In-Reply-To: <553144EB.9060701@redhat.com> On Apr 17, 2015, at 11:37 AM, John Spray <john.spray@redhat.com> wrote: > On 17/04/2015 17:22, Jan Kara wrote: >> On Fri 17-04-15 17:08:10, John Spray wrote: >>> On 17/04/2015 16:43, Jan Kara wrote: >>> In that case I'm confused -- why would ENOSPC be an appropriate use >>> of this interface if the mount being entirely blocked would be >>> inappropriate? Isn't being unable to service any I/O a more >>> fundamental and severe thing than being up and healthy but full? >>> >>> Were you intending the interface to be exclusively for data >>> integrity issues like checksum failures, rather than more general >>> events about a mount that userspace would probably like to know >>> about? >> Well, I'm not saying we cannot have those events for fs availability / >> inavailability. I'm just saying I'd like to see some use for that first. >> I don't want events to be added just because it's possible... >> >> For ENOSPC we have thin provisioned storage and the userspace deamon >> shuffling real storage underneath. So there I know the usecase. >> > > Ah, OK. So I can think of a couple of use cases: > * a cluster scheduling service (think MPI jobs or docker containers) might check for events like this. If it can see the cluster filesystem is unavailable, then it can avoid scheduling the job, so that the (multi-node) application does not get hung on one node with a bad mount. If it sees a mount go bad (unavailable, or client evicted) partway through a job, then it can kill -9 the process that was relying on the bad mount, and go run it somewhere else. > * Boring but practical case: a nagios health check for checking if mounts are OK. John, thanks for chiming in, as I was just about to write the same. Some users were just asking yesterday at the Lustre User Group meeting about adding an interface to notify job schedulers for your #1 point, and I'd much rather use a generic interface than inventing our own for Lustre. Cheers, Andreas > We don't have to invent these event types now of course, but something to bear in mind. Hopefully if/when any of the distributed filesystems (Lustre/Ceph/etc) choose to implement this, we can look at making the event types common at that time though. > > BTW in any case an interface for filesystem events to userspace will be a useful addition, thank you! > > Cheers, > John Cheers, Andreas
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Dilger <adilger@dilger.ca> To: John Spray <john.spray@redhat.com> Cc: "Jan Kara" <jack@suse.cz>, "Austin S Hemmelgarn" <ahferroin7@gmail.com>, "Beata Michalska" <b.michalska@samsung.com>, LKML <linux-kernel@vger.kernel.org>, "Theodore Ts'o" <tytso@mit.edu>, "Hugh Dickins" <hughd@google.com>, "Lukáš Czerner" <lczerner@redhat.com>, "Christoph Hellwig" <hch@infradead.org>, Ext4 <linux-ext4@vger.kernel.org>, linux-mm <linux-mm@kvack.org>, kyungmin.park@samsung.com, kmpark@infradead.org, "Linux Filesystem Mailing List" <linux-fsdevel@vger.kernel.org>, "Linux API" <linux-api@vger.kernel.org> Subject: Re: [RFC 1/4] fs: Add generic file system event notifications Date: Fri, 17 Apr 2015 16:37:32 -0600 [thread overview] Message-ID: <A8EE2778-45FE-4EC6-AB41-278D8745D068@dilger.ca> (raw) In-Reply-To: <553144EB.9060701@redhat.com> On Apr 17, 2015, at 11:37 AM, John Spray <john.spray@redhat.com> wrote: > On 17/04/2015 17:22, Jan Kara wrote: >> On Fri 17-04-15 17:08:10, John Spray wrote: >>> On 17/04/2015 16:43, Jan Kara wrote: >>> In that case I'm confused -- why would ENOSPC be an appropriate use >>> of this interface if the mount being entirely blocked would be >>> inappropriate? Isn't being unable to service any I/O a more >>> fundamental and severe thing than being up and healthy but full? >>> >>> Were you intending the interface to be exclusively for data >>> integrity issues like checksum failures, rather than more general >>> events about a mount that userspace would probably like to know >>> about? >> Well, I'm not saying we cannot have those events for fs availability / >> inavailability. I'm just saying I'd like to see some use for that first. >> I don't want events to be added just because it's possible... >> >> For ENOSPC we have thin provisioned storage and the userspace deamon >> shuffling real storage underneath. So there I know the usecase. >> > > Ah, OK. So I can think of a couple of use cases: > * a cluster scheduling service (think MPI jobs or docker containers) might check for events like this. If it can see the cluster filesystem is unavailable, then it can avoid scheduling the job, so that the (multi-node) application does not get hung on one node with a bad mount. If it sees a mount go bad (unavailable, or client evicted) partway through a job, then it can kill -9 the process that was relying on the bad mount, and go run it somewhere else. > * Boring but practical case: a nagios health check for checking if mounts are OK. John, thanks for chiming in, as I was just about to write the same. Some users were just asking yesterday at the Lustre User Group meeting about adding an interface to notify job schedulers for your #1 point, and I'd much rather use a generic interface than inventing our own for Lustre. Cheers, Andreas > We don't have to invent these event types now of course, but something to bear in mind. Hopefully if/when any of the distributed filesystems (Lustre/Ceph/etc) choose to implement this, we can look at making the event types common at that time though. > > BTW in any case an interface for filesystem events to userspace will be a useful addition, thank you! > > Cheers, > John Cheers, Andreas -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-04-17 22:37 UTC|newest] Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-15 7:15 [RFC 0/4] Generic file system events interface Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-15 7:15 ` [RFC 1/4] fs: Add generic file system event notifications Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-15 19:25 ` Darrick J. Wong 2015-04-15 19:25 ` Darrick J. Wong 2015-04-16 8:22 ` Beata Michalska 2015-04-16 8:22 ` Beata Michalska 2015-04-17 8:48 ` Jan Kara 2015-04-17 8:48 ` Jan Kara 2015-04-16 3:46 ` Eric Sandeen 2015-04-16 3:46 ` Eric Sandeen 2015-04-16 8:41 ` Beata Michalska 2015-04-16 8:41 ` Beata Michalska 2015-04-16 20:10 ` Hugh Dickins 2015-04-16 20:10 ` Hugh Dickins 2015-04-17 9:10 ` Beata Michalska 2015-04-17 9:10 ` Beata Michalska 2015-04-16 21:56 ` Heinrich Schuchardt 2015-04-16 21:56 ` Heinrich Schuchardt 2015-04-17 9:46 ` Beata Michalska 2015-04-17 9:46 ` Beata Michalska 2015-04-17 9:46 ` Beata Michalska 2015-04-17 11:58 ` Jan Kara 2015-04-17 11:58 ` Jan Kara 2015-04-17 11:31 ` Jan Kara 2015-04-17 11:31 ` Jan Kara 2015-04-17 13:04 ` Beata Michalska 2015-04-17 13:04 ` Beata Michalska 2015-04-17 13:15 ` Beata Michalska 2015-04-17 13:15 ` Beata Michalska 2015-04-17 13:16 ` Jan Kara 2015-04-17 13:16 ` Jan Kara 2015-04-17 13:16 ` Jan Kara 2015-04-17 13:23 ` Austin S Hemmelgarn 2015-04-17 13:41 ` Jan Kara 2015-04-17 13:41 ` Jan Kara 2015-04-17 14:51 ` John Spray 2015-04-17 14:51 ` John Spray 2015-04-17 15:43 ` Jan Kara 2015-04-17 15:43 ` Jan Kara 2015-04-17 16:08 ` John Spray 2015-04-17 16:08 ` John Spray 2015-04-17 16:08 ` John Spray 2015-04-17 16:22 ` Jan Kara 2015-04-17 16:22 ` Jan Kara 2015-04-17 16:22 ` Jan Kara 2015-04-17 16:29 ` Austin S Hemmelgarn 2015-04-17 16:39 ` Jan Kara 2015-04-17 16:39 ` Jan Kara 2015-04-17 16:39 ` Jan Kara 2015-04-17 17:37 ` John Spray 2015-04-17 17:37 ` John Spray 2015-04-17 22:37 ` Andreas Dilger [this message] 2015-04-17 22:37 ` Andreas Dilger 2015-04-17 16:25 ` Beata Michalska 2015-04-17 16:25 ` Beata Michalska 2015-04-17 16:25 ` Beata Michalska 2015-04-17 22:44 ` Andreas Dilger 2015-04-17 22:44 ` Andreas Dilger 2015-04-20 8:56 ` Beata Michalska 2015-04-20 8:56 ` Beata Michalska 2015-04-20 10:32 ` Jan Kara 2015-04-20 10:32 ` Jan Kara 2015-04-15 7:15 ` [RFC 2/4] ext4: Add helper function to mark group as corrupted Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-15 7:15 ` [RFC 3/4] ext4: Add support for generic FS events Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-15 19:18 ` Darrick J. Wong 2015-04-15 19:18 ` Darrick J. Wong 2015-04-16 8:02 ` Beata Michalska 2015-04-16 8:02 ` Beata Michalska 2015-04-15 7:15 ` [RFC 4/4] shmem: " Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-17 8:17 ` [RFC 0/4] Generic file system events interface Jan Kara 2015-04-17 8:17 ` Jan Kara 2015-04-17 9:10 ` Beata Michalska 2015-04-17 9:10 ` Beata Michalska
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=A8EE2778-45FE-4EC6-AB41-278D8745D068@dilger.ca \ --to=adilger@dilger.ca \ --cc=ahferroin7@gmail.com \ --cc=b.michalska@samsung.com \ --cc=hch@infradead.org \ --cc=hughd@google.com \ --cc=jack@suse.cz \ --cc=john.spray@redhat.com \ --cc=kmpark@infradead.org \ --cc=kyungmin.park@samsung.com \ --cc=lczerner@redhat.com \ --cc=linux-api@vger.kernel.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=tytso@mit.edu \ /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: linkBe 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.