From: Suman C <schakrava@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: what is the best way to monitor raid1 drive failures?
Date: Tue, 14 Oct 2014 13:11:03 -0700 [thread overview]
Message-ID: <CAPF83msoJtpRRmMEeaLHQf=e6JyoTgR9TP3p_Q5XAZCLahh-yw@mail.gmail.com> (raw)
In-Reply-To: <3E469DA1-1744-4AFC-9C56-04AE2CB6BA4F@colorremedies.com>
After the reboot step, where I indicated that I mounted ro, I was
unable to mount rw or rw,degraded. I get the "mount: wrong fs type,
bad option, bad superblock...." error if I try to mount it rw.
What might be the reason for that?
Suman
On Tue, Oct 14, 2014 at 12:15 PM, Chris Murphy <lists@colorremedies.com> wrote:
>
> On Oct 14, 2014, at 10:48 AM, Suman C <schakrava@gmail.com> wrote:
>>
>> mounted the filesystem with ro,degraded
>>
>> tried adding the "new" sdb drive which results in the following error.
>> (-f because the new drive has a fs from past)
>>
>> # btrfs device add -f /dev/sdb /mnt2/raid1pool
>> /dev/sdb is mounted
>>
>> Unless I am missing something, this looks like a bug.
>
> Strange message. I expect a device can't be added to a volume mounted ro. If the device add command works on a volume mounted rw, then the bug is the message '/dev/sdb is mounted' when adding device to ro mounted volume.
>
>
> Chris Murphy
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-14 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 23:50 what is the best way to monitor raid1 drive failures? Suman C
2014-10-13 2:21 ` Anand Jain
2014-10-13 19:50 ` Suman C
2014-10-14 2:13 ` Anand Jain
2014-10-14 14:48 ` Suman C
2014-10-14 14:52 ` Rich Freeman
2014-10-14 15:05 ` Suman C
2014-10-14 19:15 ` Chris Murphy
2014-10-14 20:11 ` Suman C [this message]
2014-10-24 16:13 ` Chris Murphy
2014-10-14 22:00 ` Duncan
2014-10-15 4:11 ` Anand Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPF83msoJtpRRmMEeaLHQf=e6JyoTgR9TP3p_Q5XAZCLahh-yw@mail.gmail.com' \
--to=schakrava@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).