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
| ||
|
Message-ID: <4874C77F.7070602@hp.com> Date: Wed, 09 Jul 2008 10:13:19 -0400 From: jim owens <jowens@...com> To: linux-fsdevel@...r.kernel.org CC: Dave Chinner <david@...morbit.com>, Theodore Tso <tytso@....edu>, Arjan van de Ven <arjan@...radead.org>, Miklos Szeredi <miklos@...redi.hu>, hch@...radead.org, pavel@...e.cz, t-sato@...jp.nec.com, akpm@...ux-foundation.org, viro@...IV.linux.org.uk, linux-ext4@...r.kernel.org, xfs@....sgi.com, dm-devel@...hat.com, linux-kernel@...r.kernel.org, axboe@...nel.dk, mtk.manpages@...glemail.com Subject: Re: [PATCH 3/3] Add timeout feature Oops.. > WHY A TIMEOUT - need a way for operator to abort the > freeze instead of "abort" I should have said "limit" because it is really proactive control (so they will not get called in the middle of the night by pissed users). I forgot to make it clear that TIMEOUT is the same as AUTO-THAW in logging errors so the adnin knows they have a bad snapshot and can do it again. I also forgot to say that our customers all say they can deal with retrying a snapshot, but not with unknown bad snapshots and most definitely not with killing their 24/7 operations! jim -- 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
Powered by blists - more mailing lists