linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Ron Johnson <ron.l.johnson@cox.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: filefrag abort
Date: Mon, 20 Jul 2009 17:16:12 -0500	[thread overview]
Message-ID: <4A64ECAC.2000900@redhat.com> (raw)
In-Reply-To: <4A64E650.6020603@cox.net>

Ron Johnson wrote:
> Hi,
> 
> (Is this OT?  http://sourceforge.net/forum/forum.php?forum_id=7052 
> doesn't show much activity...)
> 
> Debian Sid, e2fsprogs 1.41.8-1
> Home-rolled 64-bit 2.6.30 with 32-bit userland
> 
> Is this ioctl32() error caused by a "disconnect" between kernel and 
> userland?
> 
> Thanks
> 
> $ df -T /
> Filesystem    Type   1K-blocks      Used Available Use% Mounted on
> /dev/sdb2     ext3    34606072   8585632  24262528  27% /
> 
> # filefrag -v /bin/cp
> Filesystem type is: ef53
> Filesystem cylinder groups is approximately 265
> File size of /bin/cp is 92476 (23 blocks, blocksize 4096)
>   ext logical physical expected length flags
> Calling get_bmap for block 0
> Aborted
> 
> [92747.137445] ioctl32(filefrag:17217): Unknown cmd fd(3) 
> cmd(c020660b){t:'f';sz:32} arg(ffca4c38) on /bin/cp

It's a bug, I sent a patch...

http://marc.info/?l=linux-ext4&m=124768937928420&w=2

-Eric

  reply	other threads:[~2009-07-20 22:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 21:49 filefrag abort Ron Johnson
2009-07-20 22:16 ` Eric Sandeen [this message]
2009-07-21  2:03 ` Theodore Tso
2009-07-22  0:33   ` ioctl32 (was Re: filefrag abort) Ron Johnson
2009-07-22  0:57     ` Eric Sandeen
2009-07-22 17:01       ` Andreas Dilger
2009-07-23  4:51         ` Eric Sandeen
2009-07-24  0:34           ` Ron Johnson
2009-07-24  2:38             ` Eric Sandeen
2009-07-24 16:26           ` ioctl32 Andi Kleen
2009-07-24 16:28             ` ioctl32 Eric Sandeen
2009-07-25 14:46             ` ioctl32 Christoph Hellwig

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=4A64ECAC.2000900@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ron.l.johnson@cox.net \
    /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).