Hi Trent, On Tue, 30 Mar 2010, Trent W. Buck wrote: > I'm initially assigning this to dpkg because I don't know what other > tests will isolate the problem. I *am* running btrfs, but I can't > imagine how that could cause this symptom. My kernel comes from > experimental, and is not hand-rolled.
You can't imagine how an experimental filesystem could loose your data? I'm sorry, there's no way that we as dpkg maintainers are going to investigate problems that are likely to come from the filesystem itself at this point. It's possible that dpkg triggers some special cases that btrfs doesn't deal well with. I suggest you report your problems to the upstream btrfs maintainers, they are likely interested in a recipe to reproduce the data loss. But this bug should not be assigned to dpkg. You might want to reassign to the kernel but I doubt debian kernel maintainers are interested in dealing with it. IMO bugs against experimental filesystems should go upstream directly. Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
