From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id oB24Bn5c251500 for ; Wed, 1 Dec 2010 22:11:50 -0600 Received: from mail.internode.on.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 3867C160B415 for ; Wed, 1 Dec 2010 20:13:31 -0800 (PST) Received: from mail.internode.on.net (bld-mail18.adl2.internode.on.net [150.101.137.103]) by cuda.sgi.com with ESMTP id wCGnQxD6bHUsRVZq for ; Wed, 01 Dec 2010 20:13:31 -0800 (PST) Date: Thu, 2 Dec 2010 15:13:12 +1100 From: Dave Chinner Subject: Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34 Message-ID: <20101202041312.GX16922@dastard> References: <4CF661C7.2020103@sandeen.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Amit Sahrawat Cc: sandeen-xfs@sandeen.net, Eric Sandeen , xfs@oss.sgi.com On Thu, Dec 02, 2010 at 09:10:08AM +0530, Amit Sahrawat wrote: > While the copy operation is in progress, simply unplug the usb device and > then replug. That's pretty much a guaranteed recipe for data and filesystem corruption regardless of the filesystem you are using. Even if you are lucky enough that there was is no IO being issued while the device is unplugged, what guarantee is there that the device even comes back with the same device name? Further, if the device is usb powered, there is no guarantee that the drive caches were flushed correctly before the unplug so random log and metadata corruptions are definitely possible. Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs