linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Peng Tao <bergwolf@gmail.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH 1/5] e4defrag: return more specific error message on ioctl failure
Date: Sun, 19 Jul 2009 16:36:31 -0500	[thread overview]
Message-ID: <4A6391DF.3090105@redhat.com> (raw)
In-Reply-To: <1248025668-25901-1-git-send-email-bergwolf@gmail.com>

Peng Tao wrote:
> Currently e4defrag relies on the EXT4_IOC_MOVE_EXT ioctl to perform online
> defragmentation. However, this iotcl kernel patch is not available before
> 2.6.30-rc1. e4defrag shall fail without obvious reasons on systems running
> older kernels. The patch adds more detailed error message addressing this
> issue and prompts users with the minimal kernel version that is needed to
> run e4defrag.
> 
> Signed-off-by: Peng Tao <bergwolf@gmail.com>
> ---
>  misc/e4defrag.c |    6 +++++-
>  1 files changed, 5 insertions(+), 1 deletions(-)
> 
> diff --git a/misc/e4defrag.c b/misc/e4defrag.c
> index c25514a..f1c3008 100644
> --- a/misc/e4defrag.c
> +++ b/misc/e4defrag.c
> @@ -1553,7 +1553,11 @@ static int call_defrag(int fd, int donor_fd, const char *file,
>  			if (mode_flag & DETAIL) {
>  				printf("\n");
>  				PRINT_ERR_MSG_WITH_ERRNO(
> -						"Failed to defrag");
> +					"Failed to defrag with "
> +					"EXT4_IOC_MOVE_EXT ioctl");
> +				if (errno == ENOTTY)
> +					printf("\tAt least 2.6.31-rc1 of"
> +						" vallina kernel is required\n");

Typo here, s/b "vanilla"

-Eric

>  			} else {
>  				printf("\t[ NG ]\n");
>  			}


  parent reply	other threads:[~2009-07-19 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 17:47 [PATCH 1/5] e4defrag: return more specific error message on ioctl failure Peng Tao
2009-07-19 18:00 ` Peng Tao
2009-07-19 21:36 ` Eric Sandeen [this message]
2009-07-20  4:25   ` Peng Tao

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=4A6391DF.3090105@redhat.com \
    --to=sandeen@redhat.com \
    --cc=bergwolf@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).