linux-ext4 - Re: [PATCH 1/2] HACK: ext3: mount fast even when recovering

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <20090714212221.GD4829@webber.adilger.int>
Date:	Tue, 14 Jul 2009 17:22:21 -0400
From:	Andreas Dilger <adilger@....com>
To:	Adrian Hunter <adrian.hunter@...ia.com>
Cc:	akpm@...ux-foundation.org, linux-ext4@...r.kernel.org,
	Artem Bityutskiy <artem.bityutskiy@...ia.com>
Subject: Re: [PATCH 1/2] HACK: ext3: mount fast even when recovering

On Jul 14, 2009  17:03 +0300, Adrian Hunter wrote:
> Speed up ext3 recovery mount time by not sync'ing the
> block device.  Instead place all dirty buffers into the
> I/O queue and add a write barrier.  This ensures that
> no subsequent write will reach the disk before all the
> recovery writes, but that we do not have to wait for the
> I/O.
> 
> +	/*
> +	 * Set an option to indicate that we want to mount fast even
> +	 * when recovering.  That is achieved by not sync'ing the
> +	 * block device, but instead placing all dirty buffers into
> +	 * the I/O queue and adding a write barrier.
> +	 */
> +	set_opt(sbi->s_mount_opt, FAST);

Is there ever a time where one wouldn't want to do a fast mount?
Surely if this speeds things up and is safe, it makes sense to do
it always.  If it isn't safe to do always, then would you EVER want
to do it if you risk corrupting your filesystem?

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html