public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: John Twideldum <twideldums_throwaway@gmx.at>
Cc: Jan Kara <jack@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: 3.12-rc5 and overwritten partition table - by powertop?
Date: Tue, 29 Oct 2013 23:20:02 +0100	[thread overview]
Message-ID: <20131029222002.GD12814@quack.suse.cz> (raw)
In-Reply-To: <trinity-93870424-b236-4b3e-be8c-7af706430adc-1383083920353@3capp-gmx-bs31>

On Tue 29-10-13 22:58:40, John Twideldum wrote:
> >> The first ~170kb of /dev/sda got blown away with what seems to be a logging output
> >> by Powertop, when I was playing with the tuneables.
> >
> >So did you log the output to some file? I'm just trying to understand how
> >it could get onto your disk in the first place...
> 
> Attached a dump of the first 1Mb of the disk, HTH.
> It looks like a powertop log?
> (I have powertop 2.4)
  Yes, likely. But it is strange the corruption doesn't even end at any
sensible boundary (data ends at offset 0x27b53). Shrug...

> meanwhile, testdisk running in all variations recovered enough clues to
> guess the partitions correctly - the data is fine :-)
  Good.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2013-10-29 22:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 11:37 3.12-rc5 and overwritten partition table John Twideldum
2013-10-29 14:57 ` Aw: 3.12-rc5 and overwritten partition table - by powertop? John Twideldum
2013-10-29 20:10   ` Jan Kara
2013-10-29 21:58     ` John Twideldum
2013-10-29 22:20       ` Jan Kara [this message]
2013-10-29 22:32         ` John Twideldum
2014-01-21  3:08           ` Robert Hancock
2014-01-23 12:17             ` John Twideldum
2014-01-20 23:22     ` Stefan Agner
2013-10-29 20:12 ` 3.12-rc5 and overwritten partition table Jan Kara

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=20131029222002.GD12814@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twideldums_throwaway@gmx.at \
    /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