public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Bennett <andyjpb@ashurst.eu.org>
To: xfs@oss.sgi.com
Subject: Re: xfsdump quota failures
Date: Tue, 19 Jul 2016 20:03:36 +0100	[thread overview]
Message-ID: <578E7988.6020102@ashurst.eu.org> (raw)
In-Reply-To: <578E78B0.2010602@ashurst.eu.org>

Hello again,

My Google-fu failed me before I posted but, of course, succeeded
immediately after I hit send:

http://xfs.9218.n7.nabble.com/xfsdump-3-0-6-ERROR-xfs-quota-failed-with-exit-status-1-td30691.html

Does that mean that this error can be safely ignored in xfs_dump 3.0.6?



> I'm running XFS for a few filesystems under a i686 Debian Linux VPS.
> 
> Last night I upgraded from Debian Squeeze to Debian Wheezy. Before I
> started the upgrade I took a backup using xfs_dump with my usual script
> and everything went fine.
> 
> Tonight I am trying to upgrade from Debian Wheezy to Debian Jessie so I
> am taking another backup before I start.
> 
> In the logs tonight I see the following errors for file systems that
> have quotas enabled:
> 
> -----
> /usr/sbin/xfsdump: saving user quota information for: /home
> /usr/sbin/xfsdump: ERROR: xfs_quota failed with exit status: -1
> /usr/sbin/xfsdump: ERROR: failed to save user quota information, continuing
> /usr/sbin/xfsdump: saving group quota information for: /home
> /usr/sbin/xfsdump: ERROR: xfs_quota failed with exit status: -1
> /usr/sbin/xfsdump: ERROR: failed to save group quota information, continuing
> -----
> 
> -----
> /usr/sbin/xfsdump: saving user quota information for: /var
> /usr/sbin/xfsdump: ERROR: xfs_quota failed with exit status: -1
> /usr/sbin/xfsdump: ERROR: failed to save user quota information, continuing
> /usr/sbin/xfsdump: saving project quota information for: /var
> /usr/sbin/xfsdump: ERROR: xfs_quota failed with exit status: -1
> /usr/sbin/xfsdump: ERROR: failed to save project quota information,
> continuing
> -----
> 
> One of the file systems has user and group quotas enabled and the other
> has user and project quotas enabled.
> 
> The root file system is XFS but does not have quotas enabled and it
> dumps without error.
> 
> When I run xfs_quota as root by hand it gives me an interactive prompt
> and xfs_quota commands such as `df` and `print` seem to do what I would
> expect without errors.
> 
> 
> Both last night's dump and tonight's are level 0 dumps.
> 
> Last night's dump used Debian Squeeze's xfsdump 3.0.4 with xfsprogs 3.1.4.
> Tonight's dump uses Debian Wheezy's xfsdump 3.0.6 with xfsprogs 3.1.7.
> 
> 
> Can anyone give me any guidance about what's going on and how to fix it?
> 
> 
> Thanks for your help.
> 
> 
> 
> 
> Regards,
> @ndy
> 





Regards,
@ndy

-- 
andyjpb@ashurst.eu.org
http://www.ashurst.eu.org/
0290 DA75 E982 7D99 A51F  E46A 387A 7695 7EBA 75FF

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

  reply	other threads:[~2016-07-19 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 19:00 xfsdump quota failures Andy Bennett
2016-07-19 19:03 ` Andy Bennett [this message]
2016-07-19 20:24   ` Eric Sandeen
2016-07-19 20:45     ` Andy Bennett
2016-07-19 20:49       ` Eric Sandeen

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=578E7988.6020102@ashurst.eu.org \
    --to=andyjpb@ashurst.eu.org \
    --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