search for: pixley

I''m running into a situation where I can''t unmount a mounted snapshot. It shows "busy" even though neither lsof nor fuser show any open files. Umount -f doesn''t work although umount -l does. Is there anything else I can do to debug this scenario or to clear the busy status myself? Or am I down to rebooting each time? This is on stock ubuntu-10.04, x86.

Is there a limit to the number of snapshots that can exist on a file system concurrently? Did I read something here recently about a limit to the number of paths by which a file could be known? If there are limits, then what happens when I bump into or exceed that limit? --rich -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

...ime being) My home network is strung together using a Linksys Router with NAT firewall. With my current router configuration, and if I boot the Redhat machine into Windows, I am able to access the Windows shares just fine. Any info would be greatly appreciated. Thanks in advance, Dan -- Dan Pixley <danpixley@cox.net>

Christoph Hellwig wrote: > There are a lot of variables when using qemu. > > The most important one are: > > - the cache mode on the device. The default is cache=writethrough, > which is not quite optimal. You generally do want to use cache=none > which uses O_DIRECT in qemu. > - if the backing image is sparse or not. > - if you use barrier - both in the host

I'm confused about how ldap authentication is expected to work. Right now I'm seeing linux authentication work, apparently, but no samba users. [root@violet samba]# pdbedit -Lv [root@violet samba]# smbpasswd -a rpixley New SMB password: Retype new SMB password: ldapsam_search_one_group: Problem during the LDAP search: LDAP error: (No such object)ldapsam_modify_entry: Failed to add user dn= uid=rpixley,ou=People,dc=isw1,dc=symbol,dc=com with: Already exists ldapsam_add_sam_account: failed to modify/add user with...

Ubuntu-10.04, x86, stock. I''m running into a situation where a server goes pathological. Basically, it becomes excruciatingly slow. I can get things through the file system, but a simple file touch can take 6 - 12 hours. Top shows various btrfs processes hard at work - typically 100% of a cpu, (four cpu server), and the machine shows a load of just over 4. Some flush-btrfs, some