All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris" <hsvchris@gmx.de>
To: 'Eric Sandeen' <sandeen@sandeen.net>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Unexpected XFS SB number 0x00000000
Date: Tue, 11 Dec 2007 02:06:43 +0100	[thread overview]
Message-ID: <000301c83b92$191f6110$4b5e2330$@de> (raw)
In-Reply-To: 

> > 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.

I just tested some more and using parted found out the following:

(parted) print
Warning: /dev/sdb contains GPT signatures, indicating that is has a GPT
table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted --  possibly by a program that doesn't
understand GPT  partition tables. Or perhaps you deleted the GPT table, and
are now using an msdos partition table. Is this a GPT partition table?
Yes/No? y

Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number	Start		End		Size		File system	Name
Flags
1		17.4kB 	22250GB 	22250GB 	xfs


So it seems that parted can still "see" the old table. But it doesn't have
support for resizing xfs partitions...

  parent reply	other threads:[~2007-12-11  1:06 UTC|newest]

Thread overview: 10+ 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   ` AW: " Chris
2007-12-11  1:26     ` Eric Sandeen
2007-12-11  1:06   ` Chris [this message]
2007-12-11  2:12     ` Eric Sandeen
2007-12-10 22:55 ` Justin Piszcz
  -- strict thread matches above, loose matches on Subject: below --
2007-12-11 12:47 Chris
2007-04-26 19:46 Martin Eisenhardt
2007-04-26 22:57 ` Nathan Scott

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='000301c83b92$191f6110$4b5e2330$@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 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.