All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Schnelle <niklas@komani.de>
To: Yalonda Gishtaka <yalonda.gishtaka@gmail.com>
Cc: linux-btrfs@vger.kernel.org, Michael Cronenworth <mike@cchtml.com>
Subject: Re: corrupted btrfs volume: parent transid verify failed
Date: Mon, 15 Aug 2011 09:48:54 +0200	[thread overview]
Message-ID: <1313394540.1931.2.camel@pluto> (raw)
In-Reply-To: <CABqt_RMQHkzrQfPVHiL-DmWe21Y8eqjVfXEYdSDxDXWOFf3qKQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

Hi Yolanda,

are you using compression? If not and you were also using something like
LaTeX for yout thesis you could use grep to locate it on e.g. /dev/sda
then copy it out there and at least have you thesis work saved. 
I did something like that once and it worked nicely

Lg Niklas

On Mon, 2011-08-15 at 02:16 +0200, Yalonda Gishtaka wrote:
> Telling someone (that has a ~2 week stale backup) that they should
> have kept backups is hardly constructive.  We're all aware there's no
> official btrfs repair tool.  But it appears there has been been some
> hard, dedicated work towards this that has resulted in many commits
> and patches.  I'm here to find out what there is to know about recent
> developments that may help my current situation.  Please consider
> offering helpful advice instead of pointing out the obvious about my
> backup schedule.
> 
> Cheers,
> -Yalonda
> 
> On Mon, Aug 15, 2011 at 1:51 AM, Michael Cronenworth <mike@cchtml.com> wrote:
> > On 08/14/2011 06:32 PM, Yalonda Gishtaka wrote:
> >>
> >> /Helpful/  advice would be nice.
> >
> > Being hostile will net you zero advice.
> >
> --
> 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


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-08-15  7:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABqt_RND8Bd8NJ5cniKP=ySBBh6+p_xyoJh9ZL2aJeR9Sb4qrQ@mail.gmail.com>
2011-08-14 21:13 ` corrupted btrfs volume: parent transid verify failed Yalonda Gishtaka
2011-08-14 21:40   ` Fajar A. Nugraha
2011-08-14 22:05     ` Yalonda Gishtaka
2011-08-14 23:10   ` Michael Cronenworth
2011-08-14 23:32     ` Yalonda Gishtaka
     [not found]       ` <4E485F9C.8000909@cchtml.com>
2011-08-15  0:16         ` Yalonda Gishtaka
2011-08-15  7:48           ` Niklas Schnelle [this message]
2011-08-15  8:03           ` cwillu
2011-08-15  9:51             ` David Pottage

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=1313394540.1931.2.camel@pluto \
    --to=niklas@komani.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mike@cchtml.com \
    --cc=yalonda.gishtaka@gmail.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 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.