On Sat, 2015-05-23 at 16:52 +0000, Duncan wrote:
> Philip Seeger posted on Sat, 23 May 2015 14:49:50 +0200 as excerpted:
>
> > Is this a known side effect, that files could get corrupted if no
> > balance is run (not counting the balance with 4.0 which doesn't
> > work due
> > to that commit) after an ext4 conversion?
>
> I'm not sure.
>
> What I am sure of is that I'd not trust a btrfs converted from ext*
> until
> the saved subvol is deleted, and a defrag and balance run. Even
I agree. I did delete the saved subvolume right away, but given that I
effectively did not run a balance (due to this bug, the balance had no
effect) and then had new files corrupted (repeatedly) as a consequence
makes this pretty clear.
Maybe there should be a warning in the wiki ("run a complete balance
before you start using the converted fs, otherwise your files might get
corrupted.")?
Though I'd be more interested in some details as to how this might have
happened. It seems wrong that corruption occurs after a successful
conversion (before a proper balance). Is there anyone else who has had
this issue? Maybe someone who's converted to btrfs, using a btrfs
version with the balance bug?
Philip
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
