On Tue, Nov 20, 2012 at 09:25:02PM +0800, Ross Moore wrote: > Strange. Does that imply a problem with disks or disk cables physically? > Our just the data rather than the metadata? >
It seems to be a kernel bug since another user also reported it sometime ago. > I've compiled the latest btrfs-tools from git trunk add of a week ago when > I reported the bug, same results. I haven't tried an updated kernel, just > the 3.5. Should I upgrade to 3.7 rc? Will that hold any hope of change? To be honest, I'm not sure if it'll help. Hope that others can come up with where goes wrong. thanks, liubo > On 20 Nov 2012 21:20, "Liu Bo" <bo.li....@oracle.com> wrote: > > > On Tue, Nov 20, 2012 at 05:54:35PM +0800, Ross Moore wrote: > > > Hi, > > > Any update on this before I wipe the disks and start again? > > > > Hi Ross, > > > > Sorry but I failed to reproduce it locally, although I've tried various > > disk operations like balance, dev add/del etc... > > > > So have you also tried the latest btrfs or the last stable one? > > Does they show the same 'btrfs fi df' output? > > > > thanks, > > liubo > > -- 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
