[vdr] Re: VDR 1.1.20 wrong symbolic links

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Juri Haberland wrote:
> 
> Klaus Schmidinger wrote:
> > Klaudius Chlebosch wrote:
> >>
> >> Hi List,
> >>
> >> i have a really strange thing here ( vdr 1.1.20, new driver, TT_BUDGET, SuSE
> >> 7.3, /video0 and /video1 over nfs video0 is a symbolic link, server vdr 1.0.4
> >> AIO, old driver SIEMENS 1.3, TT_BUDGET, SuSE 7.3, video0 is a symbolic link ).
> >>
> >> I tried to record on RTL Der Staatsfeind...
> >>
> >> The symbolic links on /video0/... are looking strange
> >>
> >> rascal:~/bin #  ls -l
> >> /video0/Der_Staatsfeind_Nr._1/2002-12-26.20\:05.50.50.rec/
> >> total 1073
> >> drwxr-sr-x    2 vdr      video         244 Dec 26 20:18 .
> >> drwxr-sr-x    3 vdr      video          77 Dec 26 20:06 ..
> >> lrwxrwxrwx    1 vdr      video        1319 Dec 26 20:06 001.vdr ->
> >> /video1/Der_Staatsfeind_Nr._1/2002-12-26.20:05.50.50.rec/001.vdr
> 
> > Wow, I've seen something like this before, but not to such a great extent.
> > Axel Gruber had the same problem and spent quite some time tracking it down.
> > It apparently is a bug in the kernel NFS server, which I assume you are using.
> > Switch to the userspace NFS server and you should be fine.
> >
> > BTW: just for the record: this is not a VDR problem, it happens just the same
> > with the plain 'ln -s' command. I don't know if this has been fixed in newer
> > versions of the kernel NFS server.
> 
> Erm, I've never heard of such a NFS bug and I discourage the use of the
> user space NFS server. If this is really reproducable via NFS then I
> suspect more a bad interaction between the underlying file system and
> the NFS server.
> ReiserFS is my first guess - it has a long history of NFS problems...

As Axel stated in his posting it happened with ext2/3.

As far as I remember it should happen if you create a symlink with a somewhat
lengthy file name. I looked trhough my old messages but can't seem to find the
message containing the test case I believe I sent to Axel. IIRC it was absolutely
reproducable with just a simple 'ln -s' command.

@Axel: do you still remember the command(s) that reproduced this?

My guess would be:

- NFS server with /video1
- on a client do (from any directory):
  mkdir -p /video1/RaumschiffXEnterprise/2002-10-13.18:25.40.50.rec
  ln -s /video1/RaumschiffXEnterprise/2002-10-13.18:25.40.50.rec/001.vdr 001.vdr
  ls -l

If the problem occurs you should see something like

  001.vdr -> /video1/RaumschiffXEnterprise/2002-10-13.18:25.40.50.rec/001.vdr?

(note the '?' at the end).
The 'X' in the name is just to fill it up to the length where the problem happens.
If it is left out, everything is fine.

But again, this is just from memory...

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________


-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.