| 1 |
Am Thu, 18 Aug 2016 14:47:07 +0100 |
| 2 |
schrieb Neil Bothwick <neil@××××××××××.uk>: |
| 3 |
|
| 4 |
> On Thu, 18 Aug 2016 09:38:03 -0400, Rich Freeman wrote: |
| 5 |
> |
| 6 |
> > This is almost certainly a bug in btrfs-progs, or maybe the btrfs |
| 7 |
> > filesystem driver in the kernel. |
| 8 |
> |
| 9 |
> The latter, a later kernel appears to have done the trick. |
| 10 |
> |
| 11 |
> > I'd suggest raising this on the btrfs mailing list, where it is |
| 12 |
> > going to get a lot more attention from the people who develop |
| 13 |
> > btrfs. There are a few of us who use it around here, but I'd have |
| 14 |
> > to spend a day tweaking the btrfs-progs source to have a guess at |
| 15 |
> > where this is bailing out. I suspect somebody over there would |
| 16 |
> > have an answer almost immediately. |
| 17 |
> |
| 18 |
> As our resident btrfs expert, I was expecting you to come up with an |
| 19 |
> immediate answer ;-) |
| 20 |
|
| 21 |
Have you tried an explicit "btrfs dev scan"? If that helps, problems |
| 22 |
maybe arise from the udev rules... |
| 23 |
|
| 24 |
-- |
| 25 |
Regards, |
| 26 |
Kai |
| 27 |
|
| 28 |
Replies to list-only preferred. |
Archives