| To: | Amit Sahrawat <amit.sahrawat83@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34 |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 2 Dec 2010 15:13:12 +1100 |
| Cc: | Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx, sandeen-xfs@xxxxxxxxxxx |
| In-reply-to: | <AANLkTimiST8VNVsV49mniKLBudSxFj+O883Mwwe7ucac@xxxxxxxxxxxxxx> |
| References: | <AANLkTikzCpQ1j9uWGSTY9TEguVDvAB5AVYtbDtdePFci@xxxxxxxxxxxxxx> <4CF661C7.2020103@xxxxxxxxxxx> <AANLkTimiST8VNVsV49mniKLBudSxFj+O883Mwwe7ucac@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34, Amit Sahrawat |
|---|---|
| Next by Date: | Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34, Amit Sahrawat |
| Previous by Thread: | Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34, Amit Sahrawat |
| Next by Thread: | Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34, Amit Sahrawat |
| Indexes: | [Date] [Thread] [Top] [All Lists] |