All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Lista Unx <lista.unx@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: partition 100% full No space left on device. looks like xfs iscorrupted or a bug
Date: Fri, 29 Jul 2016 11:20:54 -0400	[thread overview]
Message-ID: <20160729152052.GB27744@bfoster.bfoster> (raw)
In-Reply-To: <8C01136A431C4B0AB9FC6A48220A7957@dinulap>

On Fri, Jul 29, 2016 at 05:37:19PM +0300, Lista Unx wrote:
> 
> ----- Original Message ----- From: "Brian Foster" <bfoster@redhat.com>
> To: "Lista Unx" <lista.unx@gmail.com>
> Cc: <xfs@oss.sgi.com>
> Sent: Friday, July 29, 2016 5:03 PM
> Subject: Re: partition 100% full No space left on device. looks like xfs
> iscorrupted or a bug
> 
> 
> > First and foremost, have you run 'xfs_repair -n' to see if the fs is
> > healthy? If so, the next thing I would probably try is mount from a
> > single user mode of some sort (or boot a livecd) and recheck from there
> > to rule out any OS runtime weirdness going on (open but unlinked files,
> > files hidden under mount points, etc.).
> > 
> > Brian
> > 
> 
> That's I want to do before to post here. I have access just via ssh. and
> xfs_repair require to work offline (partition to not be mounted). I do not
> have for the momment to access server using ILO (will take another few weeks
> for that) and that's the reason I post here, maybe we can coclude without
> putting server down.
> 

I guess you could kill what you can, inspect any open files with
fuser/lsof, and try to unmount as much as possible. Otherwise, I'm not
sure how far you can get until you have the ability to check the fs.
Perhaps others have more ideas...

Brian

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

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

  reply	other threads:[~2016-07-29 15:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  9:01 partition 100% full No space left on device. looks like xfs is corrupted or a bug Lista Unx
2016-07-29 10:48 ` Carlos E. R.
2016-07-29 14:27   ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 14:03 ` partition 100% full No space left on device. looks like xfs is corrupted " Brian Foster
2016-07-29 14:37   ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 15:20     ` Brian Foster [this message]
2016-07-29 21:49 ` partition 100% full No space left on device. looks like xfs is corrupted " Eric Sandeen
2016-08-01 11:24   ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 23:35 ` partition 100% full No space left on device. looks like xfs is corrupted " Dave Chinner
2016-08-01 12:00   ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-08-01 12:23     ` Carlos E. R.
2016-08-02 17:34       ` partition 100% full No space left on device. looks like xfsiscorrupted " Lista Unx
2016-08-02 17:34       ` Lista Unx
2016-08-01 16:51     ` partition 100% full No space left on device. looks like xfs iscorrupted " Chris Murphy
2016-08-02 17:58       ` partition 100% full No space left on device. looks like xfsiscorrupted " Lista Unx
2016-08-02 19:11         ` Troy McCorkell
2016-08-03 12:59     ` Spam on this list [Was: Re: partition 100% full No space left on device. looks like xfs iscorrupted or a bug] Carlos E. R.
2016-08-03 13:21       ` Martin Steigerwald
2016-08-03 13:34         ` Carlos E. R.
2016-08-03 23:15           ` Spam on this list Dave Chinner
2016-08-03 23:29             ` Darrick J. Wong
2016-08-04  0:51             ` Carlos E. R.
2016-08-04 11:34             ` Lista Unx
2016-08-04 13:40             ` Troy McCorkell
2016-08-04 15:49             ` Martin Steigerwald
2016-08-05  8:25               ` Carlos Eduardo Maiolino

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=20160729152052.GB27744@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=lista.unx@gmail.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 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.