Re: [OpenAFS] OpenAFS 1.7.601 on XP SP3, can't add Symbolic link
Using what tool? (Microsoft link command?, openafs "symlink make"?, openafs explorer extension?) In what context (what is the current path? drive letter mapping or unc path?) What permissions do you have? Please send bug reports to openafs-b...@openafs.org. Not openafs-info. On 2/21/2012 5:54 PM, David R Boldt wrote: > > Using the following values > > Link: a > Path: b > > Error window: Unable to create symbolic link: Error 0xx19 occurred. > > > -- David Boldt > > > > "Never go out to meet trouble. If you will just sit still, > nine cases out of ten someone will intercept it before it reaches you." >--Calvin Coolidge signature.asc Description: OpenPGP digital signature
[OpenAFS] OpenAFS 1.7.601 on XP SP3, can't add Symbolic link
Using the following values Link: a Path: b Error window: Unable to create symbolic link: Error 0xx19 occurred. -- David Boldt "Never go out to meet trouble. If you will just sit still, nine cases out of ten someone will intercept it before it reaches you." --Calvin Coolidge
Re: [OpenAFS] insmod failure
On 2/21/2012 11:41 AM, Simon Wilkinson wrote: On 21 Feb 2012, at 16:25, Jeff Blaine wrote: -bash-3.2# /sbin/insmod /usr/vice/etc/modload/libafs-2.6.18-308.el5.mp.ko insmod: error inserting '/usr/vice/etc/modload/libafs-2.6.18-308.el5.mp.ko': -1 Unknown symbol in module You either need to insmod exportfs first, or use depmod and modprobe. Thanks. I see the mod to afs.rc now. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] insmod failure
On 21 Feb 2012, at 16:25, Jeff Blaine wrote: > -bash-3.2# /sbin/insmod /usr/vice/etc/modload/libafs-2.6.18-308.el5.mp.ko > insmod: error inserting '/usr/vice/etc/modload/libafs-2.6.18-308.el5.mp.ko': > -1 Unknown symbol in module You either need to insmod exportfs first, or use depmod and modprobe. S. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] OpenAFS client 1.7.201 and later triggers printing of smiley faces on all printers shared via Samba
On 2012-02-20 15:53, Jeffrey Altman wrote: The log indicates a bug in Samba or the printer. The explorer shell extension is asking to open an existing file. It is explicitly asking that the file not be created if it doesn't exist and yet Samba indicates that the file does exist and has been opened. Explorer.EXE2544CreateFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._SUCCESS Desired Access: Read Data/List Directory, Write Data/Add File, Read Attributes, Synchronize, Disposition: Open, Options: Write Through, Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a, OpenResult: Opened The AFS Pioctl request is then written to the open file and when it attempts to read the result it is told that reading is an INVALID_DEVICE_REQUEST. A printer that permits writing files to the printer for the purpose of printing, faxing, etc. must only open a non-existing file if the CreateFile disposition is Create, Create_Always or Open_Always. I cannot tell for sure from this trace but I'm going to guess that the reason this behavior started with 1.7.2 is the addition of Icon Overlays for AFS mount points and symlinks. The explorer shell extension issues an AFS pioctl to test whether the device is in AFS or not. Jeffrey Altman Hi Since its all our printers that is affected (multiple different types and manufactures) we will look into the samba server. If we find anything usefull, we will report back. /Peter
Re: [OpenAFS] OpenAFS client 1.7.201 and later triggers printing of smiley faces on all printers shared via Samba
Hi Jeffrey In the attached trace.txt you can see the lines i presume gives the error The log is created as follows. start log Start -> Run -> "\\130.225.51.90" (the samba server) login to samba server in dialog window. wait for window with printers to appear. (only 1 printer on this particular test-server) stop log. The test is done twice. once with the AFS-Service running and one time with AFS-Service stopped. In the trace.txt: No_error1_filtered is with the AFS-service stopped error_filtered is the with the AFS-service running You can find the complete Process Monitor logs at //afs/ies.auc.dk/user/ped/AFS-Trace/ I did not do the wireshark logs as i presume i identified the error with the Process Monitor tool. If you need the wireshark logs let me know and i will do them Best Regards Peter Dissing Aalborg University On 2012-02-07 18:20, Jeffrey Altman wrote: On 2/7/2012 9:20 AM, Bo Nygaard Bai wrote: We have observed that windows clients running an installation of the OpenAFS client version 1.7.201 and later will, unknown to the user, print garbage on all our printers. Every time a user opens/refreshes the Samba share exporting the printers, each available printer will print 2 pages each containing a single line of output: ,\ ☺☺ How is this data arriving at the printers? You say later that the Windows Printer Spooler is disabled so there must be a direct connection from some application to the printers. Use SysInternals Process Monitor and WireShark to track the source of the data being written to the process that is doing so. In 1.7.2 the network provider interface, AFSRDFSProvider.dll, properly fails a query for printers in the \\AFS name space. It reports that there are none instead of listing the file shares. In case the above UTF-8 does not survive the mail system: Just viewing the share exporting the printers will trigger this. OpenAFS doesn't browse or otherwise interact with printers so it must be an application process doing so in response to a network provider browse request using the WNet API set. We only see this when the OpenAFS Client Service is running and only after version 1.7.201. It even happens when the windows Print Spooler service is stopped but AFS is running. If OpenAFS is halted the AFSRDFSProvider will report "not connected" to all queries. Has anybody else seen this or have an explanation? I have not. Should I file a bug report on this? With whom? That is the question. Since the problem occurs with Samba shared printers and not Microsoft Windows shared printers or Apple Bonjour shared printers, perhaps its a bug in Samba. no_error1_filtered 14:52:12,0818689svchost.exe 896 CreateFile \\130.225.51.90\pr-c1-103-bw\ CSC OBJECT PATH NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, Impersonating: ped-vm\ped error_filtered 14:33:41,3920696Explorer.EXE2544CreateFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._SUCCESS Desired Access: Read Data/List Directory, Write Data/Add File, Read Attributes, Synchronize, Disposition: Open, Options: Write Through, Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a, OpenResult: Opened 14:33:41,3983356Explorer.EXE2544WriteFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._SUCCESS Offset: 0, Length: 41, I/O Flags: Write Through, Priority: Normal 14:33:41,4042403Explorer.EXE2544ReadFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._INVALID DEVICE REQUEST Offset: 41, Length: 8.192, Priority: Normal 14:33:41,4043567Explorer.EXE2544CloseFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._SUCCESS 14:33:41,4421625Explorer.EXE2544CreateFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._SUCCESS Desired Access: Read Data/List Directory, Write Data/Add File, Read Attributes, Synchronize, Disposition: Open, Options: Write Through, Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a, OpenResult: Opened 14:33:41,4461407Explorer.EXE2544WriteFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._SUCCESS Offset: 0, Length: 41, I/O Flags: Write Through, Priority: Normal 14:33:41,4498251Explorer.EXE2544ReadFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._INVALID DEVICE REQUEST Offset: 41, Length: 8.192, Priority: Normal 14:33:41,4499010Explorer.EXE2544CloseFile \\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._SUCCESS 14:33:41,4699611svchost.exe 896 CreateFile \\130.225.51.90\pr-c1-103-bw\ CSC OBJECT PATH NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, At
[OpenAFS] insmod failure
RHEL 5.8 x86_64 with OpenAFS 1.6.0 built just now: -bash-3.2# /sbin/insmod /usr/vice/etc/modload/libafs-2.6.18-308.el5.mp.ko insmod: error inserting '/usr/vice/etc/modload/libafs-2.6.18-308.el5.mp.ko': -1 Unknown symbol in module -bash-3.2# uname -a Linux rcf-linux-beta.our.org 2.6.18-308.el5 #1 SMP Fri Jan 27 17:17:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Re: Offline volumes after upgrade to 1.6.1pre2
On 12-02-17, Andrew Deason wrote: > On Fri, 17 Feb 2012 16:50:24 +0100 > Åsa Andersson wrote: > > > It seems the typical pattern (that we missed yesterday) is that we > > first get the "inconsistent length" error for the volume and then we > > get the other error following a salvage run. > > Can you provide the SalvageLog for one of these runs? That is, for the > salvage that you did right after the 'inconsistent length' error. Here is a typical example: - SalvageLog: @(#) OpenAFS 1.6.1pre2 built 2012-01-27 02/17/2012 13:41:05 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager /vicepa 537173355 -orphans attach) 02/17/2012 13:41:07 2 nVolumesInInodeFile 56 02/17/2012 13:41:07 CHECKING CLONED VOLUME 537173357. 02/17/2012 13:41:07 home.7.u1unk8i7.backup (537173357) updated 02/10/2012 14:43 02/17/2012 13:41:07 Vnode 15302: length incorrect; (is 524288 should be 262144) 02/17/2012 13:41:07 SALVAGING VOLUME 537173355. 02/17/2012 13:41:07 home.7.u1unk8i7 (537173355) updated 02/17/2012 13:29 02/17/2012 13:41:07 Vnode 508: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 512: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 552: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 560: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 794: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 7188: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 7578: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 8154: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 8162: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 11144: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 12362: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 12384: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 12550: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 13102: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 13234: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 13486: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 13582: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 13602: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 13612: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14062: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14260: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14694: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14708: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14714: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14722: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14728: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14734: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 14832: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 15302: length incorrect; changed from 524288 to 262144 02/17/2012 13:41:07 Vnode 17074: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 17842: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 17848: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 18064: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 18922: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 20644: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 20682: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 20684: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 20702: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 21076: version < inode version; fixed (old status) 02/17/2012 13:41:07 Vnode 21358: version < inode version; fixed (old status) 02/17/2012 13:41:07 totalInodes 12437 02/17/2012 13:41:11 Attaching orphaned directory to volume's root dir as __ORPHANDIR__.1821.71626 02/17/2012 13:41:11 Attaching orphaned directory to volume's root dir as __ORPHANDIR__.1825.71348 02/17/2012 13:41:11 Attaching orphaned directory to volume's root dir as __ORPHANDIR__.1841.72791 02/17/2012 13:41:11 Attaching orphaned directory to volume's root dir as __ORPHANDIR__.1855.73645 02/17/2012 13:41:11 Attaching orphaned directory to volume's root dir as __ORPHANDIR__.3313.61428 02/17/2012 13:41:11 Vnode 1: link count incorrect (was 44, now 49) 02/17/2012 13:41:11 Vnode 67: link count incorrect (was 7, now 2) 02/17/2012 13:41:11 Vnode 1821: link count incorrect (was 1, now 2) 02/17/2012 13:41:11 Vnode 1825: link count incorrect (was 1, now 2) 02/17/2012 13:41:11 Vnode 1841: link count incorrect (was 1, now 2) 02/17/2012 13:41:11 Vnode 1855: link cou
