From: Maxim Mikheev <mikhmv@gmail.com>
To: Gareth Pye <gareth@cerberos.id.au>
Cc: cwillu <cwillu@cwillu.com>, linux-btrfs@vger.kernel.org
Subject: Re: Help with data recovering
Date: Fri, 01 Jun 2012 17:15:54 -0400 [thread overview]
Message-ID: <4FC9310A.7040609@gmail.com> (raw)
In-Reply-To: <CA+WRLO-mRoSXkdd6_ydc2py3JJCnoM4avQNanxDWWntde2Ah0A@mail.gmail.com>
Seems it does not work.
What should be a next step in data recovering?
On 05/30/2012 10:50 PM, Gareth Pye wrote:
> Stopping an experimental fsck for an exterimental file system would
> probably be the worst idea possible. I'd only think about stopping it
> after it had spent many many hours not doing anything*. If it was
> working hard after 26 hours I'd just keep working
>
> *This isn't advice to stop it if that is true, just a minimal
> condition on me stopping any fsck.
>
> On Thu, May 31, 2012 at 12:02 PM, Maxim Mikheev <mikhmv@gmail.com
> <mailto:mikhmv@gmail.com>> wrote:
>
> btrfsck --repair running already for 26 hours.
>
> Is it have sense to wait more?
>
> Thanks
>
>
> On 05/29/2012 07:36 PM, cwillu wrote:
>
> On Tue, May 29, 2012 at 5:24 PM, Maxim
> Mikheev<mikhmv@gmail.com <mailto:mikhmv@gmail.com>> wrote:
>
> Thank you for your answer.
>
>
> The system kernel was and now:
>
> Linux s0 3.4.0-030400-generic #201205210521 SMP Mon May 21
> 09:22:02 UTC 2012
> x86_64 x86_64 x86_64 GNU/Linux
>
> the raid was created by:
> mkfs.btrfs /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf
>
> Disk are connected through RocketRaid 2670.
>
> for mounting I used line in fstab:
> UUID=c9776e19-37eb-4f9c-bd6b-04e8dde97682 /tank
> btrfs
> defaults,compress=lzo 0 1
>
> On machine was running several Virtual machines. Only one
> was actively using
> disks.
>
> VM has active several threads:
> 1. 2 threads reading big files (50GB each)
> 2. reading from 50 files and writing one big file
> 3. The kernel panic happens when I run another program
> with 30 threads of
> reading/writing of small files.
>
> Virtual Machine accessed to underline btrfs through 9-p
> file system which
> actively used xattr.
>
> After reboot system was in this stage.
>
> I hope that btrfsck --repair will not make it worse, It is
> now running.
>
> **twitch**
>
> Well, I also hope it won't make it worse. Do not cancel it
> now, let
> it finish (aborting it will make things worse), but I suggest
> waiting
> until a few more people have weighed in before attempting anything
> beyond that.
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
> --
> Gareth Pye
> Level 2 Judge, Melbourne, Australia
> Australian MTG Forum: mtgau.com <http://mtgau.com/>
> gareth@cerberos.id.au <mailto:gareth@cerberos.id.au> -
> www.rockpaperdynamite.wordpress.com
> <http://www.rockpaperdynamite.wordpress.com/>
> "Dear God, I would like to file a bug report"
>
next prev parent reply other threads:[~2012-06-01 21:15 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 22:14 Help with recover data Maxim Mikheev
2012-05-29 22:40 ` Help with data recovering Maxim Mikheev
2012-05-29 23:11 ` cwillu
2012-05-29 23:24 ` Maxim Mikheev
2012-05-29 23:36 ` cwillu
2012-05-31 2:02 ` Maxim Mikheev
[not found] ` <CA+WRLO-mRoSXkdd6_ydc2py3JJCnoM4avQNanxDWWntde2Ah0A@mail.gmail.com>
2012-06-01 21:15 ` Maxim Mikheev [this message]
[not found] ` <CAGJTRcibT_pufU4tKqbBpBfm8QiuW=dhQ8BAGzQnpxMCa-dOCQ@mail.gmail.com>
2012-06-02 13:43 ` Maxim Mikheev
2012-06-04 1:22 ` Liu Bo
2012-06-04 1:43 ` Maxim Mikheev
2012-06-04 2:16 ` Liu Bo
2012-06-04 2:18 ` Maxim Mikheev
2012-06-04 2:59 ` Liu Bo
2012-06-04 3:13 ` Maxim Mikheev
2012-06-04 4:27 ` Maxim Mikheev
2012-06-04 8:18 ` Arne Jansen
2012-06-04 11:30 ` Maxim Mikheev
2012-06-04 11:32 ` Arne Jansen
2012-06-04 11:43 ` Maxim Mikheev
2012-06-04 11:49 ` Hugo Mills
2012-06-04 12:01 ` Maxim Mikheev
2012-06-04 12:11 ` Hugo Mills
2012-06-04 12:28 ` Maxim Mikheev
2012-06-04 12:34 ` Hugo Mills
2012-06-04 12:37 ` Maxim Mikheev
2012-06-04 16:24 ` Maxim Mikheev
2012-06-04 17:04 ` Hugo Mills
2012-06-04 17:09 ` Hugo Mills
2012-06-04 18:02 ` Michael
2012-06-04 18:03 ` Maxim Mikheev
2012-06-04 18:37 ` Michael
2012-06-06 16:25 ` Maxim Mikheev
2012-06-07 3:27 ` Maxim Mikheev
2012-06-05 9:55 ` Martin Steigerwald
2012-06-05 9:57 ` Martin Steigerwald
2012-06-04 14:54 ` Ryan C. Underwood
2012-06-04 16:49 ` Maxim Mikheev
2012-06-05 9:59 ` Martin Steigerwald
2012-06-05 10:23 ` Martin Steigerwald
2012-06-05 11:07 ` Helmut Hullen
2012-05-29 23:37 ` Maxim Mikheev
2012-05-29 23:14 ` Help with recover data Felix Blanke
2012-05-29 23:19 ` cwillu
2012-06-04 12:24 ` Stefan Behrens
2012-06-04 12:26 ` Maxim Mikheev
2012-06-04 13:03 ` Stefan Behrens
[not found] ` <4FCCC176.1020007@gmail.com>
2012-06-04 15:01 ` Maxim Mikheev
2012-06-04 15:02 ` Stefan Behrens
2012-06-04 15:08 ` Maxim Mikheev
2012-06-04 15:11 ` Stefan Behrens
2012-06-04 15:26 ` Maxim Mikheev
2012-06-04 17:35 ` Maxim Mikheev
2012-06-04 18:08 ` Stefan Behrens
2012-06-04 18:15 ` Ryan C. Underwood
2012-06-04 12:31 ` Maxim Mikheev
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=4FC9310A.7040609@gmail.com \
--to=mikhmv@gmail.com \
--cc=cwillu@cwillu.com \
--cc=gareth@cerberos.id.au \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.