public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: jack the ripper <evil_metalpeet@hotmail.com>
To: mw@dermichi.com
Cc: xfs@oss.sgi.com
Subject: RE: xfs_growfs doesn't grow on 2TB raid
Date: Wed, 10 Jun 2009 17:54:20 +0200	[thread overview]
Message-ID: <BAY108-W13BBC60EFE8CFE4B623CB3F3450@phx.gbl> (raw)
In-Reply-To: <4A2FAFA0.9020408@dermichi.com>


[-- Attachment #1.1: Type: text/plain, Size: 2132 bytes --]


I had not done the reboot (I'm not used to that anymore with linux). I did now though and everything is solved:

RoSe v1per # /root/mount.data1
mdadm: /dev/mddata1 has been started with 6 drives.
Enter LUKS passphrase:
key slot 0 unlocked.
Command successful.

RoSe v1per # xfs_growfs /mnt/data1/
meta-data=/dev/mapper/data1      isize=256    agcount=9, agsize=61047928 blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=488383679, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal               bsize=4096   blocks=32768, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 488383679 to 610479663

RoSe v1per # df --si
Filesystem             Size   Used  Avail Use% Mounted on
udev                    11M   349k    11M   4% /dev
shm                    1.1G      0   1.1G   0% /dev/shm
/dev/mapper/data1      2.6T   1.9T   655G  74% /mnt/data1

Thank you all for helping me so quickly and sorry for bothering all of you with the solution being so simple!

> Date: Wed, 10 Jun 2009 15:05:36 +0200
> From: mw@dermichi.com
> To: evil_metalpeet@hotmail.com
> CC: xfs@oss.sgi.com
> Subject: Re: xfs_growfs doesn't grow on 2TB raid
> 
> > Can you confirm that I need GPT for my software raid?
> You don't need GPT for software RAID unless one of your disks is >2TB. For example I am running a 3TB XFS file system directly on /dev/md0. Have you done a reboot, maybe the new size has not really been applied? Never tried it with LUKS/cryptsetup though, maybe it won't to above 2GB.
> 
> # df -h /dev/md0
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/md0              2.8T  1.5T  1.4T  53% /san1
> 
> hth Michael

_________________________________________________________________
Je hele online leven op één stek met Windows Live
http://www.microsoft.com/belux/nl/windows/windowslive/default.aspx

[-- Attachment #1.2: Type: text/html, Size: 3788 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-06-10 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 10:52 xfs_growfs doesn't grow on 2TB raid jack the ripper
2009-06-10 11:09 ` Christoph Hellwig
2009-06-10 11:22   ` jack the ripper
2009-06-10 11:44     ` Christoph Hellwig
2009-06-10 12:12 ` Emmanuel Florac
2009-06-10 12:16 ` Michael Monnerie
2009-06-10 12:30   ` jack the ripper
2009-06-10 13:05     ` Michael Weissenbacher
2009-06-10 15:54       ` jack the ripper [this message]
2009-06-10 13:37 ` Eric Sandeen
2009-06-10 15:06   ` jack the ripper
2009-06-10 15:43     ` Eric Sandeen

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=BAY108-W13BBC60EFE8CFE4B623CB3F3450@phx.gbl \
    --to=evil_metalpeet@hotmail.com \
    --cc=mw@dermichi.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox