All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Apostolov <vapo@sgi.com>
To: John Groves <John@Groves.net>
Cc: linux-xfs@oss.sgi.com, Dean Roehrich <roehrich@clink.americas.sgi.com>
Subject: Re: XFS dmapi: dm_path_to_handle fails if the path is a directory
Date: Wed, 01 Nov 2006 11:44:45 +1100	[thread overview]
Message-ID: <4547EDFD.8020407@sgi.com> (raw)
In-Reply-To: <4547DA70.4040107@Groves.net>

John Groves wrote:
> I'm running up against a difficult situation because dm_path_to_handle 
> does not return a handle, if the path is to a directory.  Is this a 
> known issue, or perhaps fixed in a recent version?  Or is there 
> another way get the handle of a directory by path?  When any file type 
> is renamed, I (for various reasons) *must* know not just the old & new 
> parent handles, but also the handle of the renamed thingy.  If the 
> thingy is a directory, I'm stuck at the moment.
>
> My test system has dmapi 2.2.1-5, which I don't think is current, but 
> I can't seem to get access to the oss.sgi.com server to check.
>
> Any advice or info appreciated.  I'm willing to try and submit a 
> patch, but I'd appreciate first knowing whether there was a specific 
> reason or problem that led to the current behavior.
>
> Thanks,
> John Groves
>
Hi John,

If your path is longer than 2000 characters dm_path_to_handle used to fail.
This bug was fixed in August 2006. Please update your tree from here:

http://oss.sgi.com/projects/xfs/download.html

Regards,
Vlad

  reply	other threads:[~2006-11-01  0:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 23:21 XFS dmapi: dm_path_to_handle fails if the path is a directory John Groves
2006-11-01  0:44 ` Vlad Apostolov [this message]
2006-11-01  0:57   ` Vlad Apostolov
2006-11-03  1:00   ` John Groves
2006-11-03  2:41     ` Vlad Apostolov
2006-11-03  2:53       ` John Groves
2006-11-03  2:59         ` Vlad Apostolov
2006-11-03 14:57           ` John Groves
2006-11-05 22:37             ` Vlad Apostolov

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=4547EDFD.8020407@sgi.com \
    --to=vapo@sgi.com \
    --cc=John@Groves.net \
    --cc=linux-xfs@oss.sgi.com \
    --cc=roehrich@clink.americas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.