Lars Schimmer wrote:
> I assumed the filemanagers are using the standard tools windows holds
> for them.
> I contacted the authors of totalcommander and asked for some help. It
> seems they calculate the "disk full" message from available space :-(
Ignoring the errors returned from a WriteFile()
On Jan 12, 2006, at 2:13 PM, Lars Schimmer wrote:
...
I assumed the filemanagers are using the standard tools windows holds
for them.
I contacted the authors of totalcommander and asked for some help. It
seems they calculate the "disk full" message from available space :-(
Now that one's OK,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd M. Lewis wrote:
>
>
> Jeffrey Altman wrote:
>
>> I have tested the functionality on Windows 2003 SP1 and everything
>> behaves exactly as it should. It doesn't matter whether I copy or
>> move from the command line or whether I drag/drop 1000
Jeffrey Altman wrote:
I have tested the functionality on Windows 2003 SP1 and everything
behaves exactly as it should. It doesn't matter whether I copy or
move from the command line or whether I drag/drop 1000 files or
whether I copy/paste files. It all works just fine.
So as far as I am co
Its 1.4.0 OAFS for win for sure.
Sorry guys, I'm in the middle of shutting a major hospital computer room
down.
Only 300 servers. If you screw up, the MIS department bars you
permanently from the facility.
If I get time later on I'll work on it. AFS that is.
Tedc
Derrick J Brashear wrote:
On Wed, 11 Jan 2006, ted creedon wrote:
I'm a tester and a user, not a debugger. I can live with the bug.
Perhaps someone else with spare time can do this.
That's not debugging. That's telling us how to reproduce your bug. If you
can't or won't, calling yourself a tester is like me calling m
I have tested the functionality on Windows 2003 SP1 and everything
behaves exactly as it should. It doesn't matter whether I copy or
move from the command line or whether I drag/drop 1000 files or
whether I copy/paste files. It all works just fine.
So as far as I am concerned there is no bug un
I'm a tester and a user, not a debugger. I can live with the bug.
Perhaps someone else with spare time can do this.
Sorry.
tedc
Jeffrey Altman wrote:
I copied in one Explorer window and Pasted to another.
Jeffrey Altman
ted creedon wrote:
PS - Did you drag'drop or cut & paste?
ted
Jef
I copied in one Explorer window and Pasted to another.
Jeffrey Altman
ted creedon wrote:
> PS - Did you drag'drop or cut & paste?
>
> ted
>
> Jeffrey Altman wrote:
>> ted creedon wrote:
>>
>>> OpenAFS 1.4.0 on all servers and clients:
>>>
>>> With XP SP2 - with all hotfixes - error box state
Ted:
Don't make assumptions based on your personal biases.
Run the SysInternal File Monitor and you will have all the data
you require.
Jeffrey Altman
ted creedon wrote:
> Give me a detailed technical explanation and a link. I don't think they
> care about AFS.
>
> ted
>
> Jeffrey Altman wr
PS - Did you drag'drop or cut & paste?
ted
Jeffrey Altman wrote:
ted creedon wrote:
OpenAFS 1.4.0 on all servers and clients:
With XP SP2 - with all hotfixes - error box states "Error in copying
file or folder->Cannot copy latexdebug" (file at which the volume filled).
WIth Win 2003 SP1 -
Give me a detailed technical explanation and a link. I don't think they
care about AFS.
ted
Jeffrey Altman wrote:
ted creedon wrote:
OpenAFS 1.4.0 on all servers and clients:
With XP SP2 - with all hotfixes - error box states "Error in copying
file or folder->Cannot copy latexdebug" (file
ted creedon wrote:
> OpenAFS 1.4.0 on all servers and clients:
>
> With XP SP2 - with all hotfixes - error box states "Error in copying
> file or folder->Cannot copy latexdebug" (file at which the volume filled).
>
> WIth Win 2003 SP1 - with all hotfixes- server the copy %complete box
> just ran
OpenAFS 1.4.0 on all servers and clients:
With XP SP2 - with all hotfixes - error box states "Error in copying
file or folder->Cannot copy latexdebug" (file at which the volume filled).
WIth Win 2003 SP1 - with all hotfixes- server the copy %complete box
just ran for 5 min after the volume w
Todd and Ted:
As a test I decided to copy a 1.9 GB file by drag drop using
XP SP2 Explorer to my home volume on athena.mit.edu. The volume
is not large enough to hold the file at all.
File h:\ (537235559.1.1) contained in cell athena.mit.edu
Owner jaltman (28180) Group 0
Volume status for vid =
ubject: Re: [OpenAFS] Windows Client, quota and filemanager - no
warning!
ted creedon wrote:
If the windows AFS client listened to the message, at least there
would
be some kind of warning.
tedc
I don't know what this is supposed to mean?
What
Jeffrey,
Your explanation of the error flows through the various levels is
informative, and I believe you are 100% right on the level you are
talking about.
From the user's perspective, however, all he sees is that he goes to
move/copy a file with the standard tools the Desktop provides, and
;>>
>>>>
>>>> ted creedon wrote:
>>>>
>>>>
>>>>> Complaints from the server that are otherwise ignored.
>>>>>
>>>>> tedc
>>>>>
>>>>> -O
, quota and filemanager - no
warning!
ted creedon wrote:
If the windows AFS client listened to the message, at least there would
be some kind of warning.
tedc
I don't know what this is supposed to mean?
What is the AFS Windows client supposed to listen to?
Je
t;
>>> -Original Message-
>>> From: [EMAIL PROTECTED]
>>> [mailto:[EMAIL PROTECTED]
>>> On Behalf Of Jeffrey Altman
>>> Sent: Tuesday, January 10, 2006 12:00 PM
>>> To: ted creedon
>>> Cc: OpenAFS-info@openafs.org
>>>
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jeffrey Altman
Sent: Tuesday, January 10, 2006 12:00 PM
To: ted creedon
Cc: OpenAFS-info@openafs.org
Subject: Re: [OpenAFS] Windows Client, quota and filemanager - no warning!
ted creedon wrote:
If the windows AFS client
alf Of Jeffrey Altman
> Sent: Tuesday, January 10, 2006 12:00 PM
> To: ted creedon
> Cc: OpenAFS-info@openafs.org
> Subject: Re: [OpenAFS] Windows Client, quota and filemanager - no warning!
>
> ted creedon wrote:
>> If the windows AFS client listened to the message, at
Complaints from the server that are otherwise ignored.
tedc
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jeffrey Altman
Sent: Tuesday, January 10, 2006 12:00 PM
To: ted creedon
Cc: OpenAFS-info@openafs.org
Subject: Re: [OpenAFS] Windows Client, quota
ted creedon wrote:
> If the windows AFS client listened to the message, at least there would
> be some kind of warning.
>
> tedc
I don't know what this is supposed to mean?
What is the AFS Windows client supposed to listen to?
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signatu
If the windows AFS client listened to the message, at least there would
be some kind of warning.
tedc
Jeffrey Altman wrote:
I should point out that the error that the OpenAFS 1.4.0 client reports
in this case is STATUS_DISK_FULL ((NTSTATUS)0xC07FL). The reason
the application is most like
I should point out that the error that the OpenAFS 1.4.0 client reports
in this case is STATUS_DISK_FULL ((NTSTATUS)0xC07FL). The reason
the application is most likely hanging is that it either does not check
the error code on the write() operation or it does not believe it.
If the application
That doen't help with the copy command. Perhaps MS should be contacted?
This is an aggravating problem, particularly with large filesystems. If
there was an RxError message from the server the client could pop up a
message box eventualy.
tedc
Jeffrey Altman wrote:
AFS is made up of volumes.
AFS is made up of volumes. CIFS file shares are contiguous disks.
It is not possible to report to Windows a different quantity of
disk space, free space, etc. on a per directory basis.
JPSoftware is the only vendor I am aware of that has added OpenAFS
support to their tools: 4NT and TakeCommand.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
One annoying problem with the windows client:
It seems not to pass the quota to the filemamagers.
E.G.: user a tries to write a 1 GB file to a volume with 400 MB quota.
User tries to use totalcommander or xplorer2. After it has copied 400 MB
the s
29 matches
Mail list logo
