From: Eric Sandeen <sandeen@sandeen.net>
To: Chris <hsvchris@gmx.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Unexpected XFS SB number 0x00000000
Date: Mon, 10 Dec 2007 16:40:22 -0600 [thread overview]
Message-ID: <475DC056.3000502@sandeen.net> (raw)
In-Reply-To: <002a01c83b74$52060330$f6120990$@de>
Chris wrote:
> Hello!
>
> I'm running a home file server with Debian GNU/Linux 4.0 4.0r1 etch
> (2.6.18-5-amd64 Kernel) and an Areca ARC-1220 hardware RAID controller.
> I used to have 4 750GB HDDs connected and set up as RAID 5 array, single
> volume, single XFS partition (set up during the installation of Debian). No
> problems so far.
>
> Now I added another 750GB HDD to the array, online capacity/volume expansion
> by the controller finished just fine.
> My plan was to add the extra space to the above mentioned XFS partition. So
> I unmounted the partition, started cfdisk, removed the partition table and
> wrote a new one that included the new free space.
> After rebooting the partition wasn't mounted, so I couldn't use xfs_growth
> to expand the filesystem.
>
> xfs_check: unexpected XFS SB magic number 0x00000000
Did your new partition table start in exactly the same place?
Can you find the string "XFSB" anywhere near where your old partition
started?
-Eric
next prev parent reply other threads:[~2007-12-10 23:20 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 [this message]
2007-12-11 0:41 ` AW: " Chris
2007-12-11 1:26 ` Eric Sandeen
2007-12-11 1:06 ` Chris
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=475DC056.3000502@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hsvchris@gmx.de \
--cc=linux-xfs@oss.sgi.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.