On Wed 17-02-16 18:02:31, Tejun Heo wrote: > On Wed, Feb 17, 2016 at 02:41:25PM -0800, Tahsin Erdogan wrote: > > With this patch, I am starting to have issues running fsck immediately > > after umount. > > > > *** fsck.ext4 output *** > > fsck from util-linux-ng 2.17.2 > > e2fsck 1.42.12-gg3 (9-Sep-2014) > > Warning! /dev/sdb3 is in use. > > Pass 1: Checking inodes, blocks, and sizes > > Deleted inode 62346243 has zero dtime. Fix? no > > Yeah, that'd be one of the side effects. Will think more about it. > Jan, do you know why we have both s_active and the rwsem at this > point? I can't tell why both are needed. I'm not sure I understand the question. Do you mean why both s_active and s_umount rwsem exist? s_active is a reference count keeping superblock alive - e.g. if the filesystem is mounted in more places, we need a reference for each mountpoint. s_umount is used when we want to block any umount operation until we are done. For example sync(2) is using it to make sure superblock doesn't disappear and so that we don't keep superblock alive after admin called umount(2). Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
