public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: tom mason <tom_in_canada@hotmail.com>
Cc: Brian Foster <bfoster@redhat.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Mount: Structure needs cleaning
Date: Mon, 13 Oct 2014 10:10:01 +1100	[thread overview]
Message-ID: <20141012231001.GC5267@dastard> (raw)
In-Reply-To: <DUB113-W8015EC9E74D26138852F2FB6AF0@phx.gbl>

[ please don't top post. ]

On Sun, Oct 12, 2014 at 10:48:36PM +0000, tom mason wrote:
> > Date: Sun, 12 Oct 2014 10:20:08 -0400
> > From: bfoster@redhat.com
> > To: tom_in_canada@hotmail.com
> > CC: xfs@oss.sgi.com
> > Subject: Re: Mount: Structure needs cleaning
> > 
> > On Sun, Oct 12, 2014 at 01:43:28AM -0700, tommason wrote:
> > > Hi,
> > > 
> > > First up - my knowledge of linux is pretty sparse - I've used it a few times
> > > before, so please be gentle!
> > > 
> > > I've had a neil poulton network space for some time now - it freaked out a
> > > while ago and I managed to rig it up to a Ubuntu liveCD via a SATA dock and
> > > rescue the files.
> > > 
> > > This has now happened again - the drive would not get out of a cycle and was
> > > not spinning properly. Bring out the dock and liveCD (this time Knoppix).
> > > All good. This time however as I eagerly copied files to another drive (a
> > > USB powered lacie rugged thing) and left it overnight i woke up to an error.
> > > I was copying around 500GB in a few diffferent chunks. The first error it
> > > reported was I think error 15? mount structure needs cleaning...
> 
> 
> > Logs? Kernel version? etc.
> 
> Hey Brian,
> Apologies! I'm pretty new to all this so you'll have to walk me through it if possible - how do I check the logs?
> 
> - Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> - xfs_repair version 3.1.9
>
> ok - so I worked out & tried the xfs_repair command:
> 
> root@ubuntu:~# xfs_repair -n /dev/sdc2
> Phase 1 - find and verify superblock...
> superblock read failed, offset 62448377856, size 131072, ag 2, rval -1
> 
> fatal error -- Input/output error

Which means the filesystem tried to read the offset at 62GB and the
underlying device failed it with EIO. That's not an XFS failure.
What error is there in dmesg when you run that xfs_repair command?

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

This asks you to post the contents of /proc/partitions, which is
what the kernel thinks are the partition sizes.

> Yes it's a NAS drive and so I assume had some kind of proprietary
> OS on the other partitions (this is where i might have messed up
> by deleting?!) I'm pretty sure that the drive in bold below (sdc2)
> is the one I'm after which is xfs...

Ummm, exactly what are you trying to do with this drive/filesystem?
What device did the drive come from in the first place?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  parent reply	other threads:[~2014-10-12 23:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12  8:43 Mount: Structure needs cleaning tommason
2014-10-12 14:20 ` Brian Foster
2014-10-12 22:39   ` tom mason
2014-10-12 22:48     ` tom mason
2014-10-12 22:51       ` tom mason
2014-10-12 23:10       ` Dave Chinner [this message]
2014-10-13 10:05         ` Tom Mason
2014-10-13 10:19           ` Emmanuel Florac
2014-10-13 10:40             ` Tom Mason
2014-10-13  9:26       ` Emmanuel Florac
  -- strict thread matches above, loose matches on Subject: below --
2014-10-13 20:33 Tom Mason
2014-10-13 22:09 ` Dave Chinner
2014-10-13 22:25   ` Tom Mason
2014-10-13 23:44     ` Dave Chinner
2014-10-13 22:38   ` Tom Mason
2014-10-13 23:47     ` Dave Chinner
2014-10-14 10:55     ` Emmanuel Florac
2014-10-14 15:46       ` Tom Mason
2014-10-14 16:38         ` Emmanuel Florac
2014-10-14 16:43           ` Tom Mason
2014-10-21 20:44           ` Tom Mason
2012-02-26  3:15 mount: " MikeJeezy
2012-02-26  4:35 ` Stan Hoeppner
2012-02-26  7:22   ` MikeJeezy
2012-02-26 17:07     ` Stan Hoeppner
2012-02-27  0:49     ` Dave Chinner
2012-02-27  3:11       ` MikeJeezy
2012-02-27  6:28         ` Stan Hoeppner
2012-02-27 18:32           ` MikeJeezy
2012-02-28  1:48         ` Dave Chinner
2012-02-28  9:14           ` Brian Candler
2012-02-29  3:50             ` Dave Chinner
2012-02-29  7:40               ` Brian Candler

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=20141012231001.GC5267@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=tom_in_canada@hotmail.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