Re: [vdr] Odd filesystem errors
Date: Sun, 22 Nov 2009 14:20:56 +0100 From: Peter Evertz l...@pec.homeip.net Subject: Re: [vdr] Odd filesystem errors To: VDR Mailing List vdr@linuxtv.org Message-ID: 4b093ab8.4000...@pec.homeip.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Klaus Schmidinger schrieb: On 07.11.2009 02:07, HighlyCaffeinated wrote: I've got an unusual situation with my VDR installation ...snip... bothersome. That is normal situation on a samba share that has (windows) illegal characters in it's name. eg: CSI: Next Session is illegal because of the : and will be translated to something like you have seen on the windows box. Peter Can you check the syslog file to see what names VDR used to create the recording directories? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Peter: I am not too concerned with the existence of a tilde in the filename. If the filename had been created per your example, I would have expected Windows to display it as CSI_Ne~1. A recent directory shows in Linux as NCIS:_Los_Angeles as it should. My concern is that I cannot see (and therefore manipulate or delete) these directories in Linux. Linux will not show the directory names or inodes. Windows does, but the names are illegal and so won't operate on them. Klaus: I will keep an eye out for the creation of any more such directories but cron took care of the syslog files long before I noticed that the directories were there. Anyone: Any clue how to delete the directories besides formatting the partition? Thanks for your help! -Todd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Odd filesystem errors
2009/11/23 HighlyCaffeinated javatod...@yahoo.com: Date: Sun, 22 Nov 2009 14:20:56 +0100 From: Peter Evertz l...@pec.homeip.net Subject: Re: [vdr] Odd filesystem errors To: VDR Mailing List vdr@linuxtv.org Message-ID: 4b093ab8.4000...@pec.homeip.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Klaus Schmidinger schrieb: On 07.11.2009 02:07, HighlyCaffeinated wrote: I've got an unusual situation with my VDR installation ...snip... bothersome. That is normal situation on a samba share that has (windows) illegal characters in it's name. eg: CSI: Next Session is illegal because of the : and will be translated to something like you have seen on the windows box. Peter Can you check the syslog file to see what names VDR used to create the recording directories? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Peter: I am not too concerned with the existence of a tilde in the filename. If the filename had been created per your example, I would have expected Windows to display it as CSI_Ne~1. A recent directory shows in Linux as NCIS:_Los_Angeles as it should. My concern is that I cannot see (and therefore manipulate or delete) these directories in Linux. Linux will not show the directory names or inodes. Windows does, but the names are illegal and so won't operate on them. Klaus: I will keep an eye out for the creation of any more such directories but cron took care of the syslog files long before I noticed that the directories were there. Anyone: Any clue how to delete the directories besides formatting the partition? Thanks for your help! -Todd what does this return ? find /video0 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Odd filesystem errors (Theunis Potgieter)
what does this return ? find /video0 Enough output that I instead chose to `find /video0 found` to more easily look through it. Careful inspection reveals those directories are not shown and find produces no errors in the process. shrugs -Todd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Odd filesystem errors (Theunis Potgieter)
On 23.11.2009 17:38, HighlyCaffeinated wrote: what does this return ? find /video0 Enough output that I instead chose to `find /video0 found` to more easily look through it. Careful inspection reveals those directories are not shown and find produces no errors in the process. This sounds very odd. Have you run an fsck on that disk, yet? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Odd filesystem errors (Theunis Potgieter)
On 23.11.2009 17:38, HighlyCaffeinated wrote: what does this return ? find /video0 Enough output that I instead chose to `find /video0 found` to more easily look through it. Careful inspection reveals those directories are not shown and find produces no errors in the process. This sounds very odd. Have you run an fsck on that disk, yet? Klaus I have. e2fsck ran against the (unmounted) volume and found no errors. I've never experienced something like this before and to be honest would not believe it if I hadn't seen it. I have successfully copied the sub-directories and data across the network using Windows/Samba, then copied it back to a new folder name. Both played perfectly. I just can't get rid of the original directories. -Todd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Odd filesystem errors (Theunis Potgieter)
On Mon, Nov 23, 2009 at 10:17 AM, HighlyCaffeinated javatod...@yahoo.com wrote: I have. e2fsck ran against the (unmounted) volume and found no errors. I've never experienced something like this before and to be honest would not believe it if I hadn't seen it. I have successfully copied the sub-directories and data across the network using Windows/Samba, then copied it back to a new folder name. Both played perfectly. I just can't get rid of the original directories. I had something similar happen a long time ago. I can't quite remember how exactly but I had to do something weird to be able to delete the directories. I can at least tell you that I found the answer by googling. Good luck. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Odd filesystem errors
On 07.11.2009 02:07, HighlyCaffeinated wrote: I've got an unusual situation with my VDR installation that has me completely stumped. My /video0 directory is located on a 1TB ext2 filesystem. When I perform an 'ls-al' I get an incomplete list of the directories located there. If I open that filesystem on a Windows box via Samba, I see that two recent directories have been created that the 'ls' does not show me. The directories are named COO66K~7 mailto:vdr@linuxtv.org(a CSI recording) and N3OZM1~R (an NCIS recording) in Windows. I can drill down into either directory and find the expected filesystem structure and two recordings that we had thought had failed. They are only visible through Windows/Samba. I can copy the contents of the directory to a Windows box and then copy them back to VDR (with a new folder name) and they play normally. As Debian refuses to acknowledge their existence, I cannot rename or delete the directories and I cannot copy data from the subdirectories. I have tried masking the tilde in the filenames, and that didn't change anything as I suspect the filenames are instead REALLY long. I am running vdr 1.7.7 with ATSC tuners and the ATSCepg plugin, and the system regularly creates successful recordings. Anyone with a pointer on how to deal with this and what may be causing such an odd set of circumstances? e2fsck didn't find anything it considered to be bothersome. Can you check the syslog file to see what names VDR used to create the recording directories? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Odd filesystem errors
Klaus Schmidinger schrieb: On 07.11.2009 02:07, HighlyCaffeinated wrote: I've got an unusual situation with my VDR installation that has me completely stumped. My /video0 directory is located on a 1TB ext2 filesystem. When I perform an 'ls-al' I get an incomplete list of the directories located there. If I open that filesystem on a Windows box via Samba, I see that two recent directories have been created that the 'ls' does not show me. The directories are named COO66K~7 mailto:vdr@linuxtv.org(a CSI recording) and N3OZM1~R (an NCIS recording) in Windows. I can drill down into either directory and find the expected filesystem structure and two recordings that we had thought had failed. They are only visible through Windows/Samba. I can copy the contents of the directory to a Windows box and then copy them back to VDR (with a new folder name) and they play normally. As Debian refuses to acknowledge their existence, I cannot rename or delete the directories and I cannot copy data from the subdirectories. I have tried masking the tilde in the filenames, and that didn't change anything as I suspect the filenames are instead REALLY long. I am running vdr 1.7.7 with ATSC tuners and the ATSCepg plugin, and the system regularly creates successful recordings. Anyone with a pointer on how to deal with this and what may be causing such an odd set of circumstances? e2fsck didn't find anything it considered to be bothersome. That is normal situation on a samba share that has (windows) illegal characters in it's name. eg: CSI: Next Session is illegal because of the : and will be translated to something like you have seen on the windows box. Peter Can you check the syslog file to see what names VDR used to create the recording directories? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
