novell share can't find file after renaming it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Undecided
|
Unassigned |
Bug Description
bzr version is 1.12
S:\Bespoke\Cashless Vending\Cashless Vending\
adding createdatabase_
bzr: ERROR: No such file: u'S:/Bespoke/
e/trunk/
he system cannot find the path specified: u'S:/Bespoke/
Vending/
fo'
bzr log says:
Thu 2009-03-05 15:07:11 +0200
0.219 bzr arguments: [u'add']
0.219 looking for plugins in C:/Documents and Settings/
0.219 looking for plugins in C:/Program Files/Bazaar/
0.360 encoding stdout as sys.stdout encoding 'cp866'
4.907 opening working tree 'S:/Bespoke/
11.172 skip control directory '.bzr'
13.391 Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
NoSuchFile: No such file: u'S:/Bespoke/
Windows Explorer can't see anything in the lock directory (even when "show hidden files" is on)
When using dir from a dos prompt, the mentioned file is there... Probably this isn't a bazaar issue at all.
here is the IRC conversation:
<loxs> http://
<mneptok> loxs: sorry, haven't used Windows in >10 years
* gabriele has quit ("Leaving.")
<loxs> me too... :(
<mneptok> not that it's a Windows issue per se, but backslashes and drive letters make me run away in fright. :)
<spiv> loxs: not sure, but what sort of network drive?
* guilhembi has quit (Read error: 110 (Connection timed out))
* guilhembi (n=guilhemb@
<loxs> spiv, it's a novell share
<spiv> loxs: it looks like the problem is something like a network drive where "mkdir mydir; touch mydir/myfile; mv mydir foo; cat foo/myfile" isn't reliable
<loxs> the strange thing is that it worked till yesterday (before reinstall of the system)
<spiv> loxs: i.e. bzr has renamed a lock directory, then gone to read the info file out of that directory (to make sure it really is the lock this process owns), and suddenly the info file is gone.
<spiv> loxs: it's quite likely to be an intermittent issue if I'm right; i.e. if you try again a couple of times it might work.
<spiv> loxs: also
<spiv> loxs: it would be interesting to know if S:/Bespoke/Cashless Vending/Cashless
<spiv> Vending/
<spiv> fo
<spiv> still exists.
<loxs> spiv, nothing in the lock directory
<spiv> loxs: hmm, interesting!
<spiv> loxs: I don't know what could cause that. It's possible that it's due to wacky network filesystem semantics, but I struggle to imagine plausible network drive behaviour that would cause that.
<loxs> you are probably right... as it used to work yesterday
<spiv> loxs: a bug report would be appreciated, though.
<loxs> spiv, what kind of information should I supply for this?
<spiv> loxs: the error message, the traceback from the bzr log file (see 'bzr version' for its location), the fact its a network share, and that the info file isn't there when you look manually
<spiv> loxs: oh, and of course that it's *novell* share :)
<loxs> ok, I'll do it now
<spiv> loxs: plus anything else you think interesting, but we can always ask for more info if necessary.
<spiv> loxs: feel free to just paste this IRC conversation into the bug report if that makes your life easier ;)
<loxs> thanks :)
<loxs> hm, spiv... in the log file... before the error you saw, there it says that it's some kind of translate error File "bzrlib\
<loxs> yesterday, the locales of my workstation were different
<spiv> loxs: that's not related to locales
<spiv> loxs: that's code for turning errors accessing files and directories from platform-specific into bzr-internal error codes.
description: | updated |
So, the info file exists, but bzr got a NoSuchFile error when it tried to read it just after renaming the containing directory.
It sounds likely that the Novell share has weird behaviour when reading a file just after renaming a directory, rather than this being a bzr fault. A bit of Googling about Novell shares isn't turning up any relevant info, though.