| Message ID | 20110126072329.GK27190@tux1.beaverton.ibm.com |
|---|---|
| State | Superseded, archived |
| Headers | show |
Hello, On Tue, Jan 25, 2011 at 11:23:29PM -0800, Darrick J. Wong wrote: > As part of migrating the FLUSH/FUA knob to the block layer, remove the support > code for the barrier-related mount options and remove the conditionals around > flushes in favor of always issuing the flush. The block layer will handle > gracefully the situation where a FLUSH or FUA request is issued to a device > that doesn't support it. Modify the option parsing code to print a warning if > someone tries to use the old mount option. > > Note: The nobarrier bit in the default mount flags is now useless. The option is something which users are already quite familiar with. I think we'll just have to carry this around. What we can do, tho, is moving the actual control mechanism to block layer - ie. blkdev_skip_flush() or something like that which ignores flush requests for the current exclusive opener. Thanks.
Hello, On Wed 26-01-11 10:36:32, Tejun Heo wrote: > On Tue, Jan 25, 2011 at 11:23:29PM -0800, Darrick J. Wong wrote: > > As part of migrating the FLUSH/FUA knob to the block layer, remove the support > > code for the barrier-related mount options and remove the conditionals around > > flushes in favor of always issuing the flush. The block layer will handle > > gracefully the situation where a FLUSH or FUA request is issued to a device > > that doesn't support it. Modify the option parsing code to print a warning if > > someone tries to use the old mount option. > > > > Note: The nobarrier bit in the default mount flags is now useless. > > The option is something which users are already quite familiar with. > I think we'll just have to carry this around. What we can do, tho, is > moving the actual control mechanism to block layer - > ie. blkdev_skip_flush() or something like that which ignores flush > requests for the current exclusive opener. Ted should have a final word about this but I believe it's possible to deprecate the mount options. Maybe with some transition period where deprecation message is shown but the option actually still works. That being said I'm not sure what we should do when someone has a disk with two partitions and one partition is mounted with barriers and another one without them - sure, one has to think hard to find a sane use case for this (possibly if user does not care about data after a crash on one of the partitions, in which case he should probably use nojournal mode) but it should probably work. Honza
Hello, On Wed, Jan 26, 2011 at 11:47:34AM +0100, Jan Kara wrote: > Ted should have a final word about this but I believe it's possible to > deprecate the mount options. Maybe with some transition period where > deprecation message is shown but the option actually still works. That > being said I'm not sure what we should do when someone has a disk with two > partitions and one partition is mounted with barriers and another one > without them - sure, one has to think hard to find a sane use case for this > (possibly if user does not care about data after a crash on one of the > partitions, in which case he should probably use nojournal mode) but it > should probably work. The policy can be made per-bdev (which maps to per-partition), so I don't think that's a big problem. Thanks.
On 01/26/2011 05:47 AM, Jan Kara wrote: > Hello, > > On Wed 26-01-11 10:36:32, Tejun Heo wrote: >> On Tue, Jan 25, 2011 at 11:23:29PM -0800, Darrick J. Wong wrote: >>> As part of migrating the FLUSH/FUA knob to the block layer, remove the support >>> code for the barrier-related mount options and remove the conditionals around >>> flushes in favor of always issuing the flush. The block layer will handle >>> gracefully the situation where a FLUSH or FUA request is issued to a device >>> that doesn't support it. Modify the option parsing code to print a warning if >>> someone tries to use the old mount option. >>> >>> Note: The nobarrier bit in the default mount flags is now useless. >> The option is something which users are already quite familiar with. >> I think we'll just have to carry this around. What we can do, tho, is >> moving the actual control mechanism to block layer - >> ie. blkdev_skip_flush() or something like that which ignores flush >> requests for the current exclusive opener. > Ted should have a final word about this but I believe it's possible to > deprecate the mount options. Maybe with some transition period where > deprecation message is shown but the option actually still works. That > being said I'm not sure what we should do when someone has a disk with two > partitions and one partition is mounted with barriers and another one > without them - sure, one has to think hard to find a sane use case for this > (possibly if user does not care about data after a crash on one of the > partitions, in which case he should probably use nojournal mode) but it > should probably work. > > Honza I would also like to suggest that mount is the right time to change a per file system behaviour. We have well known paths (add the mount options to /etc/fstab) and sys admins understand it. If we have to poke a file, what is the suggested mechanism for doing this? Another, new script or user space utility that needs to be run at mount time for each file system? If we did want to deprecate the "barrier" name, I would leave it in place and replace it with something meaningful (at mount time!) to users like "data_safety" and "no_data_safety" modes :) Ric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello, On Wed, Jan 26, 2011 at 07:16:18AM -0500, Ric Wheeler wrote: > I would also like to suggest that mount is the right time to change > a per file system behaviour. We have well known paths (add the mount > options to /etc/fstab) and sys admins understand it. > > If we have to poke a file, what is the suggested mechanism for doing > this? Another, new script or user space utility that needs to be run > at mount time for each file system? > > If we did want to deprecate the "barrier" name, I would leave it in > place and replace it with something meaningful (at mount time!) to > users like "data_safety" and "no_data_safety" modes :) With barrier on by default these days, I don't think it's necessary to fiddle with it too much. It's not as important as before. Let's leave it as it is. Barrier, flush, it doesn't really matter how it's called. In the long run tho, I think filesystems should just always enable flush/barrier and the fiddling belongs to the block layer. Thanks.
On 01/26/2011 11:47 AM, Jan Kara wrote: > Hello, > > On Wed 26-01-11 10:36:32, Tejun Heo wrote: > Ted should have a final word about this but I believe it's possible to > deprecate the mount options. Maybe with some transition period where > deprecation message is shown but the option actually still works. +1 for this from a user. I'd like to see this moved to blockdev sysfs in the long term. During the transition period there could be both the old barrier mount option (with a deprecated warning upon use) and the sysfs knobs. Flush and FUA would be delivered to disk only if both the barriers are enabled in the mount options (which is also the default) and the sysfs are at "noignore" value. Alternatively, the barrier mount option could affect the sysfs knobs values upon mount. Eventually the barrier mount option would be removed becoming always-on, leaving only the sysfs knobs. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h index 0c8d97b..fa4c688 100644 --- a/fs/ext4/ext4.h +++ b/fs/ext4/ext4.h @@ -893,7 +893,6 @@ struct ext4_inode_info { #define EXT4_MOUNT_XATTR_USER 0x04000 /* Extended user attributes */ #define EXT4_MOUNT_POSIX_ACL 0x08000 /* POSIX Access Control Lists */ #define EXT4_MOUNT_NO_AUTO_DA_ALLOC 0x10000 /* No auto delalloc mapping */ -#define EXT4_MOUNT_BARRIER 0x20000 /* Use block barriers */ #define EXT4_MOUNT_QUOTA 0x80000 /* Some quota option set */ #define EXT4_MOUNT_USRQUOTA 0x100000 /* "old" user quota */ #define EXT4_MOUNT_GRPQUOTA 0x200000 /* "old" group quota */ diff --git a/fs/ext4/super.c b/fs/ext4/super.c index 7379829..cd8e7b8 100644 --- a/fs/ext4/super.c +++ b/fs/ext4/super.c @@ -1022,13 +1022,6 @@ static int ext4_show_options(struct seq_file *seq, struct vfsmount *vfs) (unsigned) sbi->s_min_batch_time); } - /* - * We're changing the default of barrier mount option, so - * let's always display its mount state so it's clear what its - * status is. - */ - seq_puts(seq, ",barrier="); - seq_puts(seq, test_opt(sb, BARRIER) ? "1" : "0"); if (test_opt(sb, JOURNAL_ASYNC_COMMIT)) seq_puts(seq, ",journal_async_commit"); else if (test_opt(sb, JOURNAL_CHECKSUM)) @@ -1701,18 +1694,9 @@ set_qf_format: sbi->s_mount_flags |= EXT4_MF_FS_ABORTED; break; case Opt_nobarrier: - clear_opt(sb, BARRIER); - break; case Opt_barrier: - if (args[0].from) { - if (match_int(&args[0], &option)) - return 0; - } else - option = 1; /* No argument, default to 1 */ - if (option) - set_opt(sb, BARRIER); - else - clear_opt(sb, BARRIER); + ext4_msg(sb, KERN_INFO, "barrier options are " + "deprecated. Use ignore_flush in sysfs."); break; case Opt_ignore: break; @@ -3125,9 +3109,6 @@ static int ext4_fill_super(struct super_block *sb, void *data, int silent) sbi->s_min_batch_time = EXT4_DEF_MIN_BATCH_TIME; sbi->s_max_batch_time = EXT4_DEF_MAX_BATCH_TIME; - if ((def_mount_opts & EXT4_DEFM_NOBARRIER) == 0) - set_opt(sb, BARRIER); - /* * enable delayed allocation by default * Use -o nodelalloc to turn it off
As part of migrating the FLUSH/FUA knob to the block layer, remove the support code for the barrier-related mount options and remove the conditionals around flushes in favor of always issuing the flush. The block layer will handle gracefully the situation where a FLUSH or FUA request is issued to a device that doesn't support it. Modify the option parsing code to print a warning if someone tries to use the old mount option. Note: The nobarrier bit in the default mount flags is now useless. Signed-off-by: Darrick J. Wong <djwong@us.ibm.com> --- fs/ext4/ext4.h | 1 - fs/ext4/super.c | 23 ++--------------------- 2 files changed, 2 insertions(+), 22 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html