public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Lord <lord@sgi.com>
To: svetljo <galia@st-peter.stw.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: 2.4.18-rc4-aa1 XFS oopses caused by cpio
Date: Fri, 08 Mar 2002 08:30:52 -0600	[thread overview]
Message-ID: <3C88CB1C.90203@sgi.com> (raw)
In-Reply-To: <1015580766.20800.3.camel@svetljo.st-peter.stw.uni-erlangen.de> <3C88B612.1070206@sgi.com> <3C88C9A1.5070502@st-peter.stw.uni-erlangen.de>

svetljo wrote:

>
> i just created LV, formated it with xfs , extended it , mounted it, 
> extended the fs , and started to transfer my old /opt to the LV with cpio
> there were no complains from mount or xfs_growfs
> and i have no the output from mkfs.xfs
>
> [root@svetljo log]# xfs_growfs -n /opt
> meta-data=/opt            isize=256    agcount=12, agsize=33024 blks
> data     =                       bsize=4096   blocks=393216, imaxpct=25
>            =                       sunit=4      swidth=12 blks, 
> unwritten=0
>            =                       imaxbits=24
> naming   =version 2     bsize=4096
> log      =internal           bsize=4096   blocks=1200
> realtime =none            extsz=49152  blocks=0, rtextents=0
>
>
Ah, so you ran growfs on the filesystem, thats the key here. It looks 
like the new code
does not handle growfs correctly, the structure which is null is not 
allocated in the
expansion case. I should have a fix shortly.

Steve



  reply	other threads:[~2002-03-08 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-08  9:46 2.4.18-rc4-aa1 XFS oopses caused by cpio Svetoslav Slavtchev
2002-03-08 13:01 ` Stephen Lord
2002-03-08 14:24   ` svetljo
2002-03-08 14:30     ` Stephen Lord [this message]
2002-03-08 15:59       ` Stephen Lord
2002-03-10 22:19         ` Pavel Machek
2002-03-08 18:45       ` Svetoslav Slavtchev
2002-03-08 19:14         ` Martin K. Petersen

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=3C88CB1C.90203@sgi.com \
    --to=lord@sgi.com \
    --cc=galia@st-peter.stw.uni-erlangen.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox