On 2015-07-16 07:41, Austin S Hemmelgarn wrote:
On 2015-07-15 17:29, Chris Murphy wrote:
On Wed, Jul 15, 2015 at 10:15 AM, Hugo Mills wrote:
There is at least one superblock on every device, usually two, and
often three. Each superblock contains the virtual address of the roots
of the roo
On 2015-07-16 07:49, Austin S Hemmelgarn wrote:
On 2015-07-14 07:49, Austin S Hemmelgarn wrote:
So, after experiencing this same issue multiple times (on almost a
dozen different kernel versions since 4.0) and ruling out the
possibility of it being caused by my hardware (or at least, the RAM,
SA
On 2015-07-14 07:49, Austin S Hemmelgarn wrote:
So, after experiencing this same issue multiple times (on almost a dozen
different kernel versions since 4.0) and ruling out the possibility of it being
caused by my hardware (or at least, the RAM, SATA controller and disk drives
themselves), I'v
On 2015-07-15 17:29, Chris Murphy wrote:
On Wed, Jul 15, 2015 at 10:15 AM, Hugo Mills wrote:
There is at least one superblock on every device, usually two, and
often three. Each superblock contains the virtual address of the roots
of the root tree, the chunk tree and the log tree. Those ar
On Wed, Jul 15, 2015 at 10:15 AM, Hugo Mills wrote:
>There is at least one superblock on every device, usually two, and
> often three. Each superblock contains the virtual address of the roots
> of the root tree, the chunk tree and the log tree. Those are useless
> without having the chunk tr
On Wed, Jul 15, 2015 at 09:45:17AM -0600, Chris Murphy wrote:
> On Wed, Jul 15, 2015 at 5:07 AM, Austin S Hemmelgarn
> wrote:
> > I've managed to get the other filesystems I was having issues with mounted
> > again with the device= options and clear_cache after running btrfs dev scan
> > a couple
On Wed, Jul 15, 2015 at 5:07 AM, Austin S Hemmelgarn
wrote:
> I've managed to get the other filesystems I was having issues with mounted
> again with the device= options and clear_cache after running btrfs dev scan
> a couple of times. It seems to me (at least from what I'm seeing) that
> there i
On 2015-07-14 19:20, Chris Murphy wrote:
On Tue, Jul 14, 2015 at 7:25 AM, Austin S Hemmelgarn
wrote:
On 2015-07-14 07:49, Austin S Hemmelgarn wrote:
So, after experiencing this same issue multiple times (on almost a dozen
different kernel versions since 4.0) and ruling out the possibility of
On 14/07/15 11:25 PM, Austin S Hemmelgarn wrote:
On 2015-07-14 07:49, Austin S Hemmelgarn wrote:
So, after experiencing this same issue multiple times (on almost a
dozen different kernel versions since 4.0) and ruling out the
possibility of it being caused by my hardware (or at least, the RAM,
On Tue, Jul 14, 2015 at 7:25 AM, Austin S Hemmelgarn
wrote:
> On 2015-07-14 07:49, Austin S Hemmelgarn wrote:
>>
>> So, after experiencing this same issue multiple times (on almost a dozen
>> different kernel versions since 4.0) and ruling out the possibility of it
>> being caused by my hardware (
On 2015-07-14 07:49, Austin S Hemmelgarn wrote:
So, after experiencing this same issue multiple times (on almost a dozen
different kernel versions since 4.0) and ruling out the possibility of it being
caused by my hardware (or at least, the RAM, SATA controller and disk drives
themselves), I'v
So, after experiencing this same issue multiple times (on almost a dozen
different kernel versions since 4.0) and ruling out the possibility of it being
caused by my hardware (or at least, the RAM, SATA controller and disk drives
themselves), I've decided to report it here.
The general symptom
12 matches
Mail list logo
