[mythtv-users] OT: Linux problem
Hika van den Hoven
hikavdh at gmail.com
Sun Sep 27 20:42:22 UTC 2015
Hoi Damian,
Sunday, September 27, 2015, 10:30:42 PM, you wrote:
> On 27/09/2015 20:58, Hika van den Hoven wrote:
>> Hoi Damian,
>>
>> Sunday, September 27, 2015, 10:09:45 PM, you wrote:
>>
>>> On 19/09/2015 11:57, Alec Leamas wrote:
>>>> On 19/09/15 12:23, Damian wrote:
>>>>
>>>>>
>>>>> It had a bit less space than this, but I just cleared some files,
>>>>> rebooted the server, and rebooted one of my computers that connects to
>>>>> the server. It's still having the same problem, but there should be more
>>>>> than enough space on there.
>>>>>
>>>>> Any other ideas?
>>>>>
>>>>
>>>> Hm... you are using samba, right? Connecting from both Linux and
>>>> Windows clients using the SMB protocols?
>>>>
>>>> IMHO, the key is the logs. Since my installation is Fedora (and just
>>>> works ;) ) I don't have the Ubuntu setup at hand. It might be that
>>>> samba logs in /var/log/samba, dunno. But you really need to find the
>>>> server error message; the cripled information from the client can be
>>>> just any problem.
>>>>
>>>> A quick google gives me [1]. Basically, I would try something like that.
>>>>
>>>> Cheers!
>>>>
>>>> --alec
>>>>
>>>> [1] http://www.oreilly.com/openbook/samba/book/ch04_08.html
>>> Thanks for this Alec,
>>
>>> I've just looked in /var/log/samba and the most recent files in there
>>> are 7 days old. I'm having this problem multiple times per day, so it
>>> looks like an error isn't getting reported on the server end (unless I'm
>>> missing something).
>>
>>> The 7 days old files are all 0 bytes.
>>> There are also some *.1.gz files, but the most recent of them is from
>>> the 19th September.
>>
>>> I have also taken a look at the link you posted, but I'm afraid it's way
>>> beyond my level of comprehension! :-)
>>
>>> Cheers,
>>> Damian
>>
>> Are you perhaps out of inodes on your logging volume?
>> `df` gives you info about space used/free on all volumes
>> `df -i` gifes info on the inodes.
>>
>>
>> Tot mails,
>> Hika
> Hi Hika,
> Kirk solved the problem with the line Max Protocol = SMB2 in smb.conf
> However, just incase I do have a problem with my inodes, here's the
> output of those two commands ...
> $ df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 30628664 11420840 17629028 40% /
> none 4 0 4 0% /sys/fs/cgroup
> udev 3979564 4 3979560 1% /dev
> tmpfs 804732 1648 803084 1% /run
> none 5120 4 5116 1% /run/lock
> none 4023644 72 4023572 1% /run/shm
> none 102400 12 102388 1% /run/user
> /dev/sdb1 1922727728 1597370688 227665036 88% /files
> /dev/sda4 197939444 158518748 29342848 85% /tv
> $ df -i
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/sda1 1946416 245142 1701274 13% /
> none 1005911 4 1005907 1% /sys/fs/cgroup
> udev 994891 487 994404 1% /dev
> tmpfs 1005911 520 1005391 1% /run
> none 1005911 7 1005904 1% /run/lock
> none 1005911 3 1005908 1% /run/shm
> none 1005911 17 1005894 1% /run/user
> /dev/sdb1 122101760 356085 121745675 1% /files
> /dev/sda4 12582912 1383 12581529 1% /tv
> gingerserver at gingerserver-ProLiant-MicroServer:~$
> Does anything look wrong there?
> Thanks,
> Damian
Nothing problematic. As to inodes the reverse. You have many to many
on files and tv. Which is common as you mostly have big files there.
It's just a waist of space, but something you only can change at
formatting time. You need one inode for every file, so if you have a
lot of small files, you can run out. If you know you're only going to
have big files, you can allocate less space. Running out of inodes has
the same effect as running out of space. You can not save anything
anymore. Which could cause you having no logs for a week. It can for
instance happen if you due to a problem get thousands of zero byte
files in /tmp or so.
Tot mails,
Hika mailto:hikavdh at gmail.com
"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"
De lerende Mens
More information about the mythtv-users
mailing list