From: "Chris" <hsvchris@gmx.de>
To: 'Eric Sandeen' <sandeen@sandeen.net>
Cc: linux-xfs@oss.sgi.com
Subject: AW: Unexpected XFS SB number 0x00000000
Date: Tue, 11 Dec 2007 01:41:07 +0100 [thread overview]
Message-ID: <003401c83b8e$84c1d730$8e458590$@de> (raw)
In-Reply-To: <475DC056.3000502@sandeen.net>
> Did your new partition table start in exactly the same place?
>
I assumed it would be in the same place...
I guess there is no way to find out what the old one looked like?
> Can you find the string "XFSB" anywhere near where your old partition
> started?
>
I can try to do so...how? :)
When I look into the partition with cfdisk, I can see what
cylinders/heads/sectors it uses. But I'm sure there are other tools?
Interestingly, after a reboot cfdisk shows me a 801575.31 MB partition and
2199023.26 MB free space, although I wrote a single partition of 3000598.57
MB into the table before rebooting.
next prev parent reply other threads:[~2007-12-11 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 21:33 Unexpected XFS SB number 0x00000000 Chris
2007-12-10 22:40 ` Eric Sandeen
2007-12-11 0:41 ` Chris [this message]
2007-12-11 1:26 ` AW: " Eric Sandeen
2007-12-11 1:06 ` Chris
2007-12-11 2:12 ` Eric Sandeen
2007-12-10 22:55 ` Justin Piszcz
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='003401c83b8e$84c1d730$8e458590$@de' \
--to=hsvchris@gmx.de \
--cc=linux-xfs@oss.sgi.com \
--cc=sandeen@sandeen.net \
/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