From: "Lista Unx" <lista.unx@gmail.com>
To: Brian Foster <bfoster@redhat.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 17:37:19 +0300 [thread overview]
Message-ID: <8C01136A431C4B0AB9FC6A48220A7957@dinulap> (raw)
In-Reply-To: 20160729140330.GA27744@bfoster.bfoster
----- 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.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-07-29 14:37 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 ` Lista Unx [this message]
2016-07-29 15:20 ` partition 100% full No space left on device. looks like xfs iscorrupted " Brian Foster
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=8C01136A431C4B0AB9FC6A48220A7957@dinulap \
--to=lista.unx@gmail.com \
--cc=bfoster@redhat.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