Re: partially mounted cifs filesystem
On 7/7/07, Satyam Sharma <[EMAIL PROTECTED]> wrote: On 7/7/07, Albert Cahalan <[EMAIL PROTECTED]> wrote: I had one share mounted, from XP to Linux, and wanted another. At first I had an incorrect setting on the XP box, almost certainly related to permissions. The mount failed of course. Running "mount" showed that the filesystem was not mounted, but apparently it didn't remain fully unmounted either. There was also nothing under the mount point, and the "ls -l" data (directory size and link count) looked like ext3. That means nothing was mounted there ... I changed settings on the XP box numerous times. After many frustrating attempts, I ran "umount" on the mount point and then successfully mounted the filesystem. ... but still umount succeeded? Didn't it complain about nothing being mounted there in the first place? Surprising that it actually resolved the problem ... It complained, and it resolved the problem. I'll guess that the kernel returned an error for my early attempts at mounting, but left open a CIFS connection. I suppose the cifs error handling is buggy. Yes, that could be the case. Could you please: 1. Tell us which kernel version was it? .config? 2. Was there some dmesg output from the failed mount(2) attempt? 3. What was the mount command line / options? Server: Windows XP service pack 2, recently updated Client: Fedora kernel 2.6.20-1.3094.fc7, mount.cifs version 1.10 My xterm still had the commands in the scrollback buffer. I added a few, grepping dmesg and /etc/fstab, and chopped out the unrelated stuff. Note that the number in my command prompt is the exit code of the previous command; these are all correct despite editing out the unrelated commands. There are some interesting error messages, plus a lock order warning that mentions cifs. Note that I have numerous cifs shares mounted, so not every log message relates to this one. Then: 1. Rebuild kernel with CIFS_DEBUG2. 2. Revert back (on the XP share export side) to the buggy / incorrect settings -- so that you can try and reproduce the problem. 3. Let us know if you could reproduce, if so, any debug ouput / etc? I probably spent a week messing with Windows settings. I switched back and forth between simple file sharing and not, adjusted many registry settings related to anonymous/guest treatment, redid the ACLs more times than I care to think about... There really isn't any hope I could get back to the original settings. My best guess would be something related to an ACL for guest, everybody, SYSTEM, or anonymous, or something related to the checkboxes for client permissions in the file sharing dialog. At one time I had a deny ACL. Here you go. The fstab lines will be word wrapped in this email, but are not word wrapped in the file. -- proc 0 # mount /mnt/vm/sc Password: mount error 11 = Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) proc 255 # smbclient -L //192.168.1.141 Password: Domain=[ALBERTXP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment - --- IPC$IPC Remote IPC sourcecode Disk ADMIN$ Disk Remote Admin C$ Disk Default share homedir Disk session request to 192.168.1.141 failed (Called name not present) session request to 192 failed (Called name not present) Domain=[ALBERTXP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment ---- WorkgroupMaster ---- proc 0 # smbclient //192.168.1.141/sourcecode Password: Domain=[ALBERTXP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] smb: \> ls . D0 Wed Dec 6 18:12:30 2006 .. D0 Wed Dec 6 18:12:30 2006 development D0 Mon Jul 2 15:10:15 2007 legacy D0 Wed Dec 6 22:29:42 2006 libraries D0 Mon Jul 2 16:03:25 2007 mmm D0 Mon Jul 2 16:53:27 2007 re D0 Mon Jul 2 17:39:34 2007 s D0 Mon Jul 2 17:46:23 2007 thirdparty D0 Mon Jul 2 18:05:05 2007 40931 blocks of size 524288. 18955 blocks available smb: \> q proc 0 # mount /mnt/vm/sc Password: mount error 11 = Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) proc 255 # ls -l /mnt/vm/sc total 0 proc 0 # ls -l /mnt/vm total 2 drwxr-xr-x 1 root root0 2007-07-03 17:43 homedir drwxr-xr-x 2 root root 1024 2007-07-03 13:30 sc proc 0 # ls -al /mnt/vm/sc total 4 drwxr-xr-x 2 root root 1024 2007-07-03 13:30 . drwxr-xr-x 4 root root 1024 2007-07-03
Re: partially mounted cifs filesystem
On 7/7/07, Satyam Sharma [EMAIL PROTECTED] wrote: On 7/7/07, Albert Cahalan [EMAIL PROTECTED] wrote: I had one share mounted, from XP to Linux, and wanted another. At first I had an incorrect setting on the XP box, almost certainly related to permissions. The mount failed of course. Running mount showed that the filesystem was not mounted, but apparently it didn't remain fully unmounted either. There was also nothing under the mount point, and the ls -l data (directory size and link count) looked like ext3. That means nothing was mounted there ... I changed settings on the XP box numerous times. After many frustrating attempts, I ran umount on the mount point and then successfully mounted the filesystem. ... but still umount succeeded? Didn't it complain about nothing being mounted there in the first place? Surprising that it actually resolved the problem ... It complained, and it resolved the problem. I'll guess that the kernel returned an error for my early attempts at mounting, but left open a CIFS connection. I suppose the cifs error handling is buggy. Yes, that could be the case. Could you please: 1. Tell us which kernel version was it? .config? 2. Was there some dmesg output from the failed mount(2) attempt? 3. What was the mount command line / options? Server: Windows XP service pack 2, recently updated Client: Fedora kernel 2.6.20-1.3094.fc7, mount.cifs version 1.10 My xterm still had the commands in the scrollback buffer. I added a few, grepping dmesg and /etc/fstab, and chopped out the unrelated stuff. Note that the number in my command prompt is the exit code of the previous command; these are all correct despite editing out the unrelated commands. There are some interesting error messages, plus a lock order warning that mentions cifs. Note that I have numerous cifs shares mounted, so not every log message relates to this one. Then: 1. Rebuild kernel with CIFS_DEBUG2. 2. Revert back (on the XP share export side) to the buggy / incorrect settings -- so that you can try and reproduce the problem. 3. Let us know if you could reproduce, if so, any debug ouput / etc? I probably spent a week messing with Windows settings. I switched back and forth between simple file sharing and not, adjusted many registry settings related to anonymous/guest treatment, redid the ACLs more times than I care to think about... There really isn't any hope I could get back to the original settings. My best guess would be something related to an ACL for guest, everybody, SYSTEM, or anonymous, or something related to the checkboxes for client permissions in the file sharing dialog. At one time I had a deny ACL. Here you go. The fstab lines will be word wrapped in this email, but are not word wrapped in the file. -- proc 0 # mount /mnt/vm/sc Password: mount error 11 = Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) proc 255 # smbclient -L //192.168.1.141 Password: Domain=[ALBERTXP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment - --- IPC$IPC Remote IPC sourcecode Disk ADMIN$ Disk Remote Admin C$ Disk Default share homedir Disk session request to 192.168.1.141 failed (Called name not present) session request to 192 failed (Called name not present) Domain=[ALBERTXP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment ---- WorkgroupMaster ---- proc 0 # smbclient //192.168.1.141/sourcecode Password: Domain=[ALBERTXP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] smb: \ ls . D0 Wed Dec 6 18:12:30 2006 .. D0 Wed Dec 6 18:12:30 2006 development D0 Mon Jul 2 15:10:15 2007 legacy D0 Wed Dec 6 22:29:42 2006 libraries D0 Mon Jul 2 16:03:25 2007 mmm D0 Mon Jul 2 16:53:27 2007 re D0 Mon Jul 2 17:39:34 2007 s D0 Mon Jul 2 17:46:23 2007 thirdparty D0 Mon Jul 2 18:05:05 2007 40931 blocks of size 524288. 18955 blocks available smb: \ q proc 0 # mount /mnt/vm/sc Password: mount error 11 = Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) proc 255 # ls -l /mnt/vm/sc total 0 proc 0 # ls -l /mnt/vm total 2 drwxr-xr-x 1 root root0 2007-07-03 17:43 homedir drwxr-xr-x 2 root root 1024 2007-07-03 13:30 sc proc 0 # ls -al /mnt/vm/sc total 4 drwxr-xr-x 2 root root 1024 2007-07-03 13:30 . drwxr-xr-x 4 root root 1024 2007-07-03 13:30 .. proc 0
Re: partially mounted cifs filesystem
Hi Albert, [ added linux-cifs-client to Cc: ] On 7/7/07, Albert Cahalan <[EMAIL PROTECTED]> wrote: I had one share mounted, from XP to Linux, and wanted another. At first I had an incorrect setting on the XP box, almost certainly related to permissions. The mount failed of course. Running "mount" showed that the filesystem was not mounted, but apparently it didn't remain fully unmounted either. There was also nothing under the mount point, and the "ls -l" data (directory size and link count) looked like ext3. That means nothing was mounted there ... I changed settings on the XP box numerous times. After many frustrating attempts, I ran "umount" on the mount point and then successfully mounted the filesystem. ... but still umount succeeded? Didn't it complain about nothing being mounted there in the first place? Surprising that it actually resolved the problem ... I'll guess that the kernel returned an error for my early attempts at mounting, but left open a CIFS connection. I suppose the cifs error handling is buggy. Yes, that could be the case. Could you please: 1. Tell us which kernel version was it? .config? 2. Was there some dmesg output from the failed mount(2) attempt? 3. What was the mount command line / options? Then: 1. Rebuild kernel with CIFS_DEBUG2. 2. Revert back (on the XP share export side) to the buggy / incorrect settings -- so that you can try and reproduce the problem. 3. Let us know if you could reproduce, if so, any debug ouput / etc? Thanks, Satyam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: partially mounted cifs filesystem
Hi Albert, [ added linux-cifs-client to Cc: ] On 7/7/07, Albert Cahalan [EMAIL PROTECTED] wrote: I had one share mounted, from XP to Linux, and wanted another. At first I had an incorrect setting on the XP box, almost certainly related to permissions. The mount failed of course. Running mount showed that the filesystem was not mounted, but apparently it didn't remain fully unmounted either. There was also nothing under the mount point, and the ls -l data (directory size and link count) looked like ext3. That means nothing was mounted there ... I changed settings on the XP box numerous times. After many frustrating attempts, I ran umount on the mount point and then successfully mounted the filesystem. ... but still umount succeeded? Didn't it complain about nothing being mounted there in the first place? Surprising that it actually resolved the problem ... I'll guess that the kernel returned an error for my early attempts at mounting, but left open a CIFS connection. I suppose the cifs error handling is buggy. Yes, that could be the case. Could you please: 1. Tell us which kernel version was it? .config? 2. Was there some dmesg output from the failed mount(2) attempt? 3. What was the mount command line / options? Then: 1. Rebuild kernel with CIFS_DEBUG2. 2. Revert back (on the XP share export side) to the buggy / incorrect settings -- so that you can try and reproduce the problem. 3. Let us know if you could reproduce, if so, any debug ouput / etc? Thanks, Satyam - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
partially mounted cifs filesystem
I had one share mounted, from XP to Linux, and wanted another. At first I had an incorrect setting on the XP box, almost certainly related to permissions. The mount failed of course. Running "mount" showed that the filesystem was not mounted, but apparently it didn't remain fully unmounted either. There was also nothing under the mount point, and the "ls -l" data (directory size and link count) looked like ext3. I changed settings on the XP box numerous times. After many frustrating attempts, I ran "umount" on the mount point and then successfully mounted the filesystem. I'll guess that the kernel returned an error for my early attempts at mounting, but left open a CIFS connection. I suppose the cifs error handling is buggy. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
partially mounted cifs filesystem
I had one share mounted, from XP to Linux, and wanted another. At first I had an incorrect setting on the XP box, almost certainly related to permissions. The mount failed of course. Running mount showed that the filesystem was not mounted, but apparently it didn't remain fully unmounted either. There was also nothing under the mount point, and the ls -l data (directory size and link count) looked like ext3. I changed settings on the XP box numerous times. After many frustrating attempts, I ran umount on the mount point and then successfully mounted the filesystem. I'll guess that the kernel returned an error for my early attempts at mounting, but left open a CIFS connection. I suppose the cifs error handling is buggy. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
