On 10/12/2014 9:28 μμ, Marc Joliet wrote:
Am Wed, 10 Dec 2014 10:51:15 +0800
schrieb Anand Jain :
Is there any relevant log in the dmegs ?
Not in my case; at least, nothing that made it into the syslog.
Same with me, no messages at all
--
To unsubscribe from this list: send the line "unsu
Am Wed, 10 Dec 2014 10:51:15 +0800
schrieb Anand Jain :
> Is there any relevant log in the dmegs ?
Not in my case; at least, nothing that made it into the syslog.
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
signatu
Is there any relevant log in the dmegs ?
On 09/12/2014 20:16, Konstantinos Skarlatos wrote:
I've got the exact same problem, with a 4 drive RAID1. kernel 3.18-git
and btrfs tools-git, all built yesterday.
On 22/11/2014 2:13 μμ, Marc Joliet wrote:
Hi all,
While I haven't gotten any "scrub
I've got the exact same problem, with a 4 drive RAID1. kernel 3.18-git
and btrfs tools-git, all built yesterday.
On 22/11/2014 2:13 μμ, Marc Joliet wrote:
Hi all,
While I haven't gotten any "scrub already running" type errors any more, I do
get one strange case of state misreport. When runnin
Hi all,
While I haven't gotten any "scrub already running" type errors any more, I do
get one strange case of state misreport. When running scrub on /home (btrfs
RAID10), after 3 of 4 drives have completed, the 4th drive (sdb) will report as
interrupted, despite still running:
# btrfs scrub stat