All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Andreas.Klauer@metamorpher.de
Cc: xfs@oss.sgi.com
Subject: Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Structure needs cleaning
Date: Fri, 19 Jul 2013 13:37:15 +1000	[thread overview]
Message-ID: <20130719033715.GR11674@dastard> (raw)
In-Reply-To: <20130718165103.Horde.2fnDfu2TMCHHT7990c6Vqw2@webmail.df.eu>

On Thu, Jul 18, 2013 at 04:51:03PM +0200, Andreas.Klauer@metamorpher.de wrote:
> Quoting Dave Chinner <david@fromorbit.com>:
> >Have you recently upgraded from an older kernel (i.e. older than 3.9)?
> 
> Sorry, I think I missed this question.
> 
> I update about once a month to latest stable from kernel.org.

Ok, so the verifiers have been there for a while. Next question
-when was the last time you tried to grow the filesystem?

> 3.8.5 (April) -> 3.9.0 (May) -> 3.9.4 (June) -> 3.10.0 (July 1st) ->
> 3.10.1 (July 15th)
> 
> So no "older" kernels really. In case something really goes south I
> have good backups...

I happy to hear someone say that ;)

As it is, can you do an XFS event trace trace when you attempt to
grow the filesystem and send the output of the trace to me? See
here:

http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F

for where to get trace-cmd and how to run it to gather the event
trace.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

      reply	other threads:[~2013-07-19  3:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 11:04 xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Structure needs cleaning Andreas Klauer
2013-07-18 11:13 ` Dave Chinner
2013-07-18 11:29   ` Andreas Klauer
2013-07-18 12:45     ` Dave Chinner
2013-07-18 13:18       ` Andreas.Klauer
2013-07-18 14:51       ` Andreas.Klauer
2013-07-19  3:37         ` Dave Chinner [this message]

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=20130719033715.GR11674@dastard \
    --to=david@fromorbit.com \
    --cc=Andreas.Klauer@metamorpher.de \
    --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 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.