"scrub" stops the machine
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hallo, Arne,
Du meintest am 17.03.12 zum Thema Re: "scrub" stops the machine:
Quoted 9 lines · Helmut Hullen
Quoted 6 lines
btrfs scrub start
/mnt/btrand all was dead. Really dead. No access via keybord, no access via SSH.
what kernel are you using?
As mentioned some hours ago: 3.2.9 (self made).
Quoted 1 line
Are you by any chance on a 32 bit maschine?
Yes.
Viele Gruesse!
Helmut
Am Samstag, 17. M=E4rz 2012 schrieb Helmut Hullen:
Quoted 1 line
Hallo, Arne,
Hi Helmut, Arne, Chris, hi everyone,
Quoted 5 lines
Du meintest am 17.03.12 zum Thema Re: "scrub" stops the machine:
Quoted 4 lines · Helmut Hullen
Quoted 3 lines
btrfs scrub start
/mnt/btr
=20
and all was dead. Really dead. No access via keybord, no access vi=
a
Quoted 9 lines
Quoted 3 lines
Quoted 1 line
SSH.
=20
what kernel are you using?=20
As mentioned some hours ago: 3.2.9 (self made).
=20Quoted 1 line
Are you by any chance on a 32 bit maschine?
=20
Yes.
Please review the thread I started with subject:
3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot
I had the same issue, but with some recent 3.2 debian kernel it went aw= ay=20
and then the scrub just hang - process in D state. And a patch from Chr= is=20
fixed that.
Arne had two patches to test that he thought might fix the lock up hard= =20
issue, but I didn=B4t need those.
Ciao,
--=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hallo, Martin,
Du meintest am 17.03.12:
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
btrfs scrub start
/mnt/btrand all was dead. Really dead. No access via keybord, no access via SSH.
Kernel 3.2.9
[...]
Quoted 3 lines
Please review the thread I started with subject:
3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot
Your system has run for some seconds and has sent messages. My syste seems to die immediately after receiving "scrub start".
Viele Gruesse!
Helmut
Am Samstag, 17. M=E4rz 2012 schrieb Helmut Hullen:
Quoted 10 lines
Du meintest am 17.03.12:
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
btrfs scrub start
/mnt/btr
=20
and all was dead. Really dead. No access via keybord, no access via SSH.=20
Kernel 3.2.9
=20
[...]
=20
Quoted 6 lines
Quoted 3 lines
Please review the thread I started with subject:
=20
3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot=20
Your system has run for some seconds and has sent messages. My syste seems to die immediately after receiving "scrub start".
Initially mine did as well as I wrote in the initial posting.
Then possibly after some kernel upgrade, I did a btrfs filesystem balan= ce=20
on it and then the scrub didn=B4t die immediately, but got stuck. Did y= ou=20
try whether a balance works?
Maybe 3.2.10 oder 3.2.11 contains some related fixes? But then I don=B4= t=20
think that the Debian Wheezy kernel already has 3.2.10 or 3.2.11.
Ciao,
--=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 1 line · On Monday 19 March 2012 19:22:58 Martin Steigerwald wrote:
Maybe 3.2.10 oder 3.2.11 contains some related fixes?
I don't believe that any btrfs fixes get pushed to the stable releases (at least, not yet), you'll need 3.3 for newer code.
cheers,
Chris
Signature · 4 lines
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP
Am Montag, 19. M=C3=A4rz 2012 schrieb Chris Samuel:
Quoted 4 lines · On Monday 19 March 2012 19:22:58 Martin Steigerwald wrote:
Quoted 1 line
Maybe 3.2.10 oder 3.2.11 contains some related fixes?
=20
I don't believe that any btrfs fixes get pushed to the stable release=
s
Quoted 1 line
(at least, not yet), you'll need 3.3 for newer code.
Well maybe the second btrfs filesystem balance call or a possible upgra= de=20
of btrfs-tools fixed it for me. Cause I didn=C2=B4t do anything specifi= c to fix=20
the hard lock up issue. The getting stuck issue Chris Mason fixed by wi= th=20
casting patch.
Ciao,
--=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hallo, Martin,
Du meintest am 17.03.12:
Quoted 5 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
btrfs scrub start
/mnt/btrand all was dead. Really dead. No access via keybord, no access via SSH.
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
what kernel are you using?
As mentioned some hours ago: 3.2.9 (self made).
Quoted 1 line
Are you by any chance on a 32 bit maschine?
Yes.
Second try with kernel 3.2.5: same problem.
The system is completely dead.
Viele Gruesse!
Helmut
Quoted 1 line · On Sunday 18 March 2012 19:04:00 Helmut Hullen wrote:
Second try with kernel 3.2.5: same problem.
My understanding is that all 3.2.x versions will have the same btrfs code, if you want to try with a newer version you'll need to try the 3.3 release candidates.
cheers!
Chris
Signature · 4 lines
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP