| To: | submit@xxxxxxxxxxxxxxx |
|---|---|
| Subject: | Bug#664550: xfs_quota: "report -p" doesn't show all projects |
| From: | Sergio Gelato <Sergio.Gelato@xxxxxxxxxxx> |
| Date: | Sun, 18 Mar 2012 22:11:11 +0100 |
| Delivered-to: | submit@xxxxxxxxxxxxxxx |
| Reply-to: | Sergio Gelato <Sergio.Gelato@xxxxxxxxxxx>, 664550@xxxxxxxxxxxxxxx |
| Resent-cc: | XFS Development Team <xfs@xxxxxxxxxxx> |
| Resent-date: | Sun, 18 Mar 2012 21:16:49 +0000 |
| Resent-from: | Sergio Gelato <Sergio.Gelato@xxxxxxxxxxx> |
| Resent-message-id: | <handler.664550.B.133210510920574@xxxxxxxxxxxxxxx> |
| Resent-sender: | Debian BTS <debbugs@xxxxxxxxxxxxxxxxx> |
| Resent-to: | debian-bugs-dist@xxxxxxxxxxxxxxxx |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
Package: xfsprogs Version: 3.1.4 When invoked without an explicit -U argument, the report and dump subcommands of xfs_quota only mention projects that have a corresponding entry in /etc/projid . This important fact is not mentioned in the man page. It could easily result in loss of quota limit information across dump/restore on systems where /etc/projid is out of date, corrupt or missing. (Aside: even the fact that the dump subcommand accepts -L and -U isn't documented in the man page. Why not?) With an explicit -U, the code switches from getprent() (which iterates over the contents of /etc/projid) to a simple loop over all project IDs in the given range. This is better, except possibly for performance if the project ID space is sparse. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: raid10n2/xfs setup guidance on write-cache/barrier, Peter Grandi |
|---|---|
| Next by Date: | NotificaciÃn webmaster!!ââ, Webmaster ActualizaciÃn Departamento |
| Previous by Thread: | NotificaciÃn webmaster!!ââ, Webmaster ActualizaciÃn Departamento |
| Next by Thread: | Download the attachment and get back to me, Susan Shabangu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |