Re: RE : Mounting samba 2.2.7a from Linux read-write hazardous
On Tue, 2003-03-25 at 14:01, COLLOT Jean-Yves wrote: > The problem is that sometimes some other utility opens the file in write > mode but never writes anything in the file. It seems that the Linux smbfs > stuff does that a lot. However, you can reproduce the same problem with a > Windows XP PC by right-clicking "Properties" on a file on a read/write > share. For some unknown reason, this action opens the file in write mode, so > changes the "variable" to "stream", but does not write anything in the file > itself. Such unexpected behaviour may happen with other kind of PC clients. I see. Yes, I have just reproduced the bug with Properties on Win XP. Evil. Since I'm unsure of which other PC apps we may have in use which depend on being able to open files on the VMS shares in write mode, we'll be reverting to Pathworks 5 until you have a proper fix rather than applying your patch. It seems the safest alternative and the one with the least impact on our users for now. Looking forward to the complete fix. Thanks for your quick response on this problem. Ben -- Ben Armstrong-. Medianet Development Group, [EMAIL PROTECTED] `-.Dymaxion Research Limited http://www.dymaxion.ca/>`- Halifax, Nova Scotia, Canada PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
RE : Mounting samba 2.2.7a from Linux read-write hazardous
> the mere act of reading files can change the file type, > leading to corruption of the data when viewed or edited. The original > file type was Sequential, Variable, Carriage return carriage control. > The type gets munged from Variable to Stream Actually, you just have discovered some quite alarming bug... Samba-VMS sometimes changes Variable-record files to Stream files (Pathworks does that too). This change is supposed to be done only when the variable-record file is modified and then re-written by some utility on the PC side (such as Wordpad, Notepad, ...). It does that because when rewriting the file, it writes a stream-structured information, so you must do that if you want the file to be readable afterwards. The problem is that sometimes some other utility opens the file in write mode but never writes anything in the file. It seems that the Linux smbfs stuff does that a lot. However, you can reproduce the same problem with a Windows XP PC by right-clicking "Properties" on a file on a read/write share. For some unknown reason, this action opens the file in write mode, so changes the "variable" to "stream", but does not write anything in the file itself. Such unexpected behaviour may happen with other kind of PC clients. I plan to do additional analysis and hopefully fixing of this problem as soon as possible. In the meantime, I have posted on the usual URL (http://www.pi-net.dyndns.org/anonymous/jyc/) a file names PATCH-VAR-STM.ZIP (at the bottom of the page), which contains a backup save-set containing a (speedy) correction. This correction stops all changes from VAR to STREAM. Notepad or Wordpad changes of VAR files will not work anymore, but at least it prevents unwanted changes. To apply that patch, please do the following : - Unzip the file, then BACKUP/RESTORE the resulting BCK. You'll get 2 files, named STM_READ.OBJ and STM_READ.C. The C file is not really useful. - Put the STM_READ.OBJ in the SAMBA.OLB library, which is situated in the [.SOURCE.BIN] area ($ LIB [.BIN]SAMBA.OLB STM_READ.OBJ) - Relink SMBD, by executing "@[.SOURCE.VMS]LINK.COM NODEBUG SMBD" - Copy the resulting new [.SOURCE.BIN]SMBD.EXE file into the SAMBA_ROOT:[BIN] area - Stop all SMBD_* processes. I am really sorry about that problem, and I just can't understand that neither me nor other people using Samba-VMS has not seen it before. Note, however, that there is no harm done to the data inside the file. In the case of erroneous structure change, the harm can be undone by executing SET FILE/ATTR=RFM:VAR for that file. PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Mounting samba 2.2.7a from Linux read-write hazardous
On Tue, 2003-03-25 at 11:17, Ben Armstrong wrote: > I will be first downgrading smbfs to see if this is only a bug in my > bleeding-edge version on not. Any other suggestions would be > appreciated. I have downgraded my smbfs to a much earlier, stable release: 2.2.3a and can still reproduce the file type munging bug with that version. This would seem to make it less likely that smbfs is the source of the bug (although again it doesn't entirely rule out the possibility). Ben -- Ben Armstrong-. Medianet Development Group, [EMAIL PROTECTED] `-.Dymaxion Research Limited http://www.dymaxion.ca/>`- Halifax, Nova Scotia, Canada PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Mounting samba 2.2.7a from Linux read-write hazardous
Hi, I'm helping Rod Regier here at Dymaxion to evaluate Samba 2.2.7a. After an extensive debugging/testing period we have finally "flipped the switch" this morning and changed over from Pathworks V to Samba on our main Alpha/VMS server. The very first problem I noticed was quite alarming, so I thought I'd drop a note here in case anyone else has a similar system. When I use Linux 2.4.20 + smbfs 2.999+3.0.alpha21-5 (Debian "unstable" release - note, quite "bleeding edge") to mount a drive from the Alpha/VMS Samba 2.2.7a server, the mere act of reading files can change the file type, leading to corruption of the data when viewed or edited. The original file type was Sequential, Variable, Carriage return carriage control. The type gets munged from Variable to Stream. The file doesn't merely look incorrect on the Linux client, it is actually modified on the server. When I modify the file attributes to restore it to Variable, the file no longer looks corrupted. My workaround is to mount the Samba shares read-only. I cannot reproduce this problem from a W2K workstation. I have not yet ruled out a smbfs bug, but it is perhaps interesting to note that I have had many months of trouble-free operation of smbfs (even using 2.999+3.0.alpha21) until the switch from Pathworks V to Samba 2.2.7a. I will be first downgrading smbfs to see if this is only a bug in my bleeding-edge version on not. Any other suggestions would be appreciated. Thanks, Ben -- Ben Armstrong-. Medianet Development Group, [EMAIL PROTECTED] `-.Dymaxion Research Limited http://www.dymaxion.ca/>`- Halifax, Nova Scotia, Canada PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
[no subject]
subscribe samba-vms Julian Loaring Julian H J Loaring, MCTA/ES4c Assessment Software Support NN: 93 80 25693 BT: 023 9272 5693 PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
