[Bug 165245] KDE does not start on CIFS-mounted home directories (lockfile problem)

[bjoern at cs.tu-berlin.de]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=165245         




------- Additional Comments From bjoern cs tu-berlin de  2008-06-29 13:03 -------
Here are some additional notes for linux-cifs support. My testing is still based on samba-3.0.26a-3.7 (Server) and cifs-mount-3.0.26a-3.7 (Client) on Linux (openSUSE 10.3). Other setups (for instance Windows server) may produce other results.

- hard links could be created on the remote CIFS site
  # ln file1 link1

- on the server site the newly created links are really hard links
  # ls -li file1 link1
  48843 -rw-r--r-- 2 bv bv 0 29. Jun 12:34 file1
  48843 -rw-r--r-- 2 bv bv 0 29. Jun 12:34 link1

- on the server site "file1" and "link1" both have the same link count, 
  but not the same inode number. 
  # ls -li file1 link1
  43502 -rw-r--r-- 2 bv bv 0 29. Jun 12:34 file1
  43503 -rw-r--r-- 2 bv bv 0 29. Jun 12:34 link1

- The inode numbers are not based on the server inode numbers. Other each 
  new mount the inode numbers may change on the client site:
  # cd /
  # sudo umount /home
  # sudo mount -t cifs //chemnitz/bv /home/bv -o username=bv
  Password:
  # cd
  # ls -li file1 link1
  47570 -rw-r--r-- 2 bv bv 0 29. Jun 12:34 file1
  47575 -rw-r--r-- 2 bv bv 0 29. Jun 12:34 link1

This behavior results in the fact that 

231    if (!linkCountSupport &&
232        (KDE_lstat(lckFile, &st_buf2) == 0) && st_buf == st_buf2)

is false on CIFS, because st_buf is not st_buf2 (the inode numbers do not match).