linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Chris Murphy <lists@colorremedies.com>
Cc: Zach Brown <zab@redhat.com>, Nick Lee <email@nickle.es>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Question: How can I recover this partition? (unable to find logical $hugenum len 4096)
Date: Thu, 29 Aug 2013 20:53:22 +0100	[thread overview]
Message-ID: <20130829195322.GS3115@carfax.org.uk> (raw)
In-Reply-To: <0E1979CF-25EC-47B2-B74E-9870F3D9C626@colorremedies.com>

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

On Thu, Aug 29, 2013 at 01:44:54PM -0600, Chris Murphy wrote:
> 
> On Aug 29, 2013, at 1:40 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> 
> > On Thu, Aug 29, 2013 at 01:37:51PM -0600, Chris Murphy wrote:
> >> 
> >> "Proceeding will roll back the file system to a previous state, and may cause the loss of successfully written data. Proceed? (Y/N)"
> > 
> >   "... the loss of up to the last 30 seconds of successfully written data."
> > 
> >   Give the user enough information to make a sensible decision.
> 
> Certainly, if known for sure it won't be more than 30 seconds?

   Mmm... it'll depend on the setting of the commit period, which up
until a couple of weeks ago was always 30s, but someone posted a patch
to give it a config knob...

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
        --- emacs:  Eighty Megabytes And Constantly Swapping. ---        

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-08-29 19:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22  6:47 Question: How can I recover this partition? (unable to find logical $hugenum len 4096) Nicholas Lee
2013-08-22 14:09 ` Mitch Harder
2013-08-22 19:23   ` Nicholas Lee
2013-08-22 19:38     ` Nicholas Lee
2013-08-22 22:58       ` Chris Murphy
2013-08-23  0:58         ` Chris Murphy
     [not found]           ` <6A12FF1B-5E1A-4F6F-92DA-41E52152E6F2@nickle.es>
2013-08-26 17:26             ` Nicholas Lee
2013-08-26 17:36               ` Chris Murphy
     [not found]                 ` <CAGURm2FS=YTuBpbrg7BV=Un8ZCp9xYZae-WuqhjV29xXA7e0jw@mail.gmail.com>
2013-08-26 19:10                   ` Chris Murphy
2013-08-26 19:31                     ` Hugo Mills
2013-08-27  3:39                       ` Chris Murphy
2013-08-29 17:35                       ` Zach Brown
2013-08-29 19:37                         ` Chris Murphy
2013-08-29 19:40                           ` Hugo Mills
2013-08-29 19:44                             ` Chris Murphy
2013-08-29 19:53                               ` Hugo Mills [this message]
2013-08-29 20:19                                 ` Chris Murphy
2013-08-29 20:28                                   ` Chris Murphy
2013-08-30 14:44                                   ` Eric Sandeen
2013-08-30 14:54                                     ` Hugo Mills
2013-08-23  0:59         ` Nicholas Lee
2013-08-23  1:26           ` Chris Murphy
2013-08-22 23:53 ` Duncan
     [not found] ` < pan$c2c58$61dbf027$55d0c5a2$71b9b679@cox.net>
2013-08-23  1:47   ` Duncan

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=20130829195322.GS3115@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=email@nickle.es \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=zab@redhat.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).