>
The problem is that you can't do that if there's not enough space on
the remaining devices to hold all the data.
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Graphics Project
--
To unsub
On Wed, Aug 19, 2015 at 1:22 AM, Qu Wenruo wrote:
>
>
> Timothy Normand Miller wrote on 2015/08/18 22:55 -0400:
>>
>> On Tue, Aug 18, 2015 at 10:48 PM, Qu Wenruo
>> wrote:
>>>
>>>
>>>
>>> Timothy Normand Miller wrote on 2015/08/18
On Tue, Aug 18, 2015 at 10:48 PM, Qu Wenruo wrote:
>
>
> Timothy Normand Miller wrote on 2015/08/18 22:46 -0400:
>>
>> On Tue, Aug 18, 2015 at 9:32 PM, Qu Wenruo
>> wrote:
>>>
>>> Hi Timothy,
>>>
>>> Although I have replied to the
t
died, which was replaced by a new one, but btrfs wouldn't finish the
deletion of the missing device.
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Graphics Project
--
To unsubscribe from this list: se
I was doing it on an unmounted volume anyhow.
On Tue, Aug 18, 2015 at 5:09 PM, Chris Murphy wrote:
> On Tue, Aug 18, 2015 at 5:21 AM, Austin S Hemmelgarn
> wrote:
>> On 2015-08-17 14:52, Timothy Normand Miller wrote:
>>>
>>> I'm not sure if I'm d
Never mind on that last lsattr question. I needed a "-d" option. Silly me. :)
On Tue, Aug 18, 2015 at 1:39 PM, Timothy Normand Miller
wrote:
> Another weird thing I've noticed. I did this:
>
> chattr +C /mnt/btrfs/vms
>
> But both of these report nothing:
>
Another weird thing I've noticed. I did this:
chattr +C /mnt/btrfs/vms
But both of these report nothing:
lsattr /mnt/btrfs/vms
lsattr /mnt/vms
Shouldn't at least one show the C attribute?
On Tue, Aug 18, 2015 at 1:36 PM, Timothy Normand Miller
wrote:
> Maybe this is a dumb
a /mnt/btrfs/vms (via the
/mnt/btrfs mount point) and /mnt/vms (where the subvolume is mounted).
I applied +C to /mnt/btrfs/vms. So what I'm trying to find out is if
it also applies when files are accessed via /mnt/vms.
Thanks.
--
Timothy Normand Miller, PhD
Assistant Professor of Computer
I've filed a bug report on this:
https://bugzilla.kernel.org/show_bug.cgi?id=103081
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Graphics Project
--
To unsubscribe from this list: send the
M, Timothy Normand Miller
wrote:
> In that case, do I need to do all four block devices separately, or
> will the tool figure it out?
>
> On Tue, Aug 18, 2015 at 7:21 AM, Austin S Hemmelgarn
> wrote:
>> On 2015-08-17 14:52, Timothy Normand Miller wrote:
>>>
>>> I
In that case, do I need to do all four block devices separately, or
will the tool figure it out?
On Tue, Aug 18, 2015 at 7:21 AM, Austin S Hemmelgarn
wrote:
> On 2015-08-17 14:52, Timothy Normand Miller wrote:
>>
>> I'm not sure if I'm doing this wrong. Here's
ote:
> On 2015-08-15 17:46, Timothy Normand Miller wrote:
>>
>> To those of you who have been helping out with my 4-drive RAID1
>> situation, is there anything further we should do to investigate this,
>> in case we can uncover any more bugs, or should I just wipe everyth
To those of you who have been helping out with my 4-drive RAID1
situation, is there anything further we should do to investigate this,
in case we can uncover any more bugs, or should I just wipe everything
out and restore from backup?
--
Timothy Normand Miller, PhD
Assistant Professor of
Here's the associated bug report with the full dmesg:
https://bugzilla.kernel.org/show_bug.cgi?id=102941
On Sat, Aug 15, 2015 at 9:13 AM, Timothy Normand Miller
wrote:
> So I tried deleting the files that I think are the problem, and the
> file system went suddenly read-only, and I
] [] ? kthread_create_on_node+0x180/0x180
[39710.420036] [] ? ret_from_fork+0x42/0x70
[39710.420037] [] ? kthread_create_on_node+0x180/0x180
[39710.420038] ---[ end trace 0b4fe6057cd7a1a4 ]---
On Sat, Aug 15, 2015 at 9:13 AM, Timothy Normand Miller
wrote:
> So I tried deleting the files that I think are
sdc) in
btrfs_run_delayed_refs:2821: errno=-2 No such entry
[39710.431108] pending csums is 5795840
On Sat, Aug 15, 2015 at 8:51 AM, Timothy Normand Miller
wrote:
> I didn't quite understand "profile and convert", since I can't find a
> profile option. Is this something y
art of VM.
>
>>> After applying Anand's patch, I was able to mount my 4-drive RAID1
>>> and bring a new fourth drive online.
>
>>> However, something weird happened
>>> where the first "delete missing" only deleted one missing drive and
>>>
BTW, when this is all over with, how do I make sure there are really
two copies of everything? Will a scrub verify this? Should I run a
balance operation?
On Fri, Aug 14, 2015 at 11:29 PM, Timothy Normand Miller
wrote:
> After applying Anand's patch, I was able to mount my 4-drive R
report here:
https://bugzilla.kernel.org/show_bug.cgi?id=102901
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Graphics Project
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
t
14141/
>
> its on 4.3. but should apply nice on below.
>
> thanks
> Anand
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Graphics Project
--
To unsubscribe from this list: send the line "
t; [PATCH 23/23] Btrfs: allow -o rw,degraded for single group profile
>
Where is this patch, and what kernel versions can this be applied to?
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Gr
I'm not sure my situation is quite like the one you linked, so here's
my bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=102881
On Fri, Aug 14, 2015 at 2:44 PM, Chris Murphy wrote:
> On Fri, Aug 14, 2015 at 12:12 PM, Timothy Normand Miller
> wrote:
>> Sorry abou
ed on the NUMBER of missing devices, that it won't mount.
Shouldn't it refuse to mount if it knows there is data missing? For
that matter, why should it even refuse in that case? So some data
might missing, so it should throw some errors if you try to access
that missing data. Right?
Tha
My
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Graphics Project
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kerne
ead and order a new drive. Meanwhile, is there a
way to add and remove drives from volumes that can't be mounted?
On Wed, Aug 12, 2015 at 4:48 PM, Timothy Normand Miller
wrote:
> Actually, it didn't resume. The "btrfs delete missing" was using 100%
> of the I/O ba
FS bytes used 1.46TiB
devid2 size 931.51GiB used 767.00GiB path /dev/sdd
devid3 size 931.51GiB used 745.03GiB path /dev/sdc
devid4 size 931.51GiB used 767.00GiB path /dev/sdb
*** Some devices missing
btrfs-progs v4.1.2
On Wed, Aug 12, 2015 at 4:27
It resumed on its own. Weird.
On Wed, Aug 12, 2015 at 4:23 PM, Timothy Normand Miller
wrote:
> On Wed, Aug 12, 2015 at 2:10 PM, Chris Murphy wrote:
>
>>
>> Anyway it looks like it's hardware related, but I don't know what
>> device ata4.00 is, so maybe t
that had appeared
to have bad sectors. So it looks like either this new motherboard has
a bad connector, or the cable is bad. I'm going to swap it out for a
different SATA cable. How do I resume the failed operation? And
should I reboot because of the OOPSes?
--
Timothy Normand M
2" here:
https://bugzilla.kernel.org/show_bug.cgi?id=102691
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Graphics Project
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs&quo
se. I'm guessing it wouldn't be worth it to add a
feature like this because (a) few people use nodatacow or end up in my
situation, and (b) if they did, and the two copies were inconsistent,
what would you do? I suppose for me, it would be nice to know which
files were affected.
RAID5 was even partially implemented.
There is still data redundancy. Will a scrub at least notice that the
copies differ?
--
Timothy Normand Miller, PhD
Assistant Professor of Computer Science, Binghamton University
http://www.cs.binghamton.edu/~millerti/
Open Graphics Project
--
To unsubscribe from
On Tue, Aug 11, 2015 at 3:57 PM, Chris Murphy wrote:
> On Tue, Aug 11, 2015 at 12:04 PM, Timothy Normand Miller
> wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=102691
>
> [7.729124] BTRFS: device fsid ecdff84d-b4a2-4286-a1c1-cd7e5396901c
> devid 2
lently:
# btrfs scrub status /mnt/btrfs/
scrub status for ecdff84d-b4a2-4286-a1c1-cd7e5396901c
scrub started at Tue Aug 11 13:56:36 2015 and was aborted after 01:31:55
total bytes scrubbed: 2.19TiB with 0 errors
No new messages appeared in dmesg, so I can't tell why it aborted.
It's a
On Tue, Aug 11, 2015 at 1:56 PM, Timothy Normand Miller
wrote:
> On Tue, Aug 11, 2015 at 12:21 AM, Chris Murphy
> wrote:
>> The entire dmesg is still useful because it should show libata errors
>> if these aren't fully failed drives. So you should file a bug and
>
On Tue, Aug 11, 2015 at 12:21 AM, Chris Murphy wrote:
> On Mon, Aug 10, 2015 at 7:23 PM, Timothy Normand Miller
> wrote:
>> On Mon, Aug 10, 2015 at 6:52 PM, Chris Murphy
>> wrote:
>
>>> - complete dmesg for the failed mount
>>
>> It really
>
>
> --
> Chris Murphy
> --
> 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
--
Timothy Normand Miller, PhD
A
LOTS of trouble with 4-drive RAID1. I get OOPSes regularly.
I've tried reporting them on bugzilla.kernel.org, but it doesn't
appear that btrfs devs actually use that. Is this list a better place
to report those?
Thanks for the help!
--
Timothy Normand Miller, PhD
Assistant Profe
37 matches
Mail list logo
