NAS drive odd behavior and Gigabit question

[Husse]

I'll try to answer this
<<
I don't think the way you mount wakes up the NAS - but I may be wrong
What exactly does this mean?

I have noticed periodically the drive wakes up without any activity.

Check the system logs > messages Every twenty minutes (can be changed but that is the default) the syslog daemon writes --MARK-- to show it's awake
If you have placed the logs on the NAS, well ....
There may be other daemons that write on a regular schedule
<<

Do I need to remove the "0 0" at the end

Let them be - or it will not mount (well it does not necessary have to be zeros)
See man fstab fstab has and extensive man page
<<
The permissions problem - is is just for images?
The mount is in home with user in the line so you should own the NAS unless there are folders belonging to someone else in it
Be careful with sudo if you try to fix this so you do not unintentionally make root the owner - I've made that mistake a couple of times
<<
mtu 7500 careful - you want come an inch on the internet with that mtu I think
But if that's no problem it's fairly easy to fix - see
http://forums.linuxmint.com/viewtopic.p ... =a#p127456
but that gives the new mtu to that interface so if it's used for internet.....
<<
I think you can disable the built in card in BIOS
If not run lspci -v to identify which module and driver it uses
It is then possible to blacklist these if they are not used by something else

[Husse]

I have much to do right now and I don't quite understand the problem so I'll have to think about it and come back to you
You should not have permissions problem for yourself as it's mounted - maybe others though
Check the permissions setting of the NAS - you could right click and make sure you and the group have read and write permissions

[Husse]

Here's a description for Ubuntu 8.04
http://www.marcus-furius.com/?p=59
Similar to your solution, but the line in fstab explicitly declares the permissions
I have found at least one explanation to part of the wake up problem
Mint makes a (hidden) trash folder .Trash-1000 in a partition you have deleted something in - not sure about that, in some but not all partitions
That folder is a "sub set" of "normal" trash - they are linked - and when you throw something in the trash bin all the trash reacts
There may be other files or folders that do this - check the NAS for hidden files

[Husse]

I'm lost here - will call for help

[Boo]

OK on seeing this I first thought automount not fstab.
remember too some indexing service may check the fs at regular intervals including the nas mount (ie wake it up).

so checkout:
http://www.howtoforge.com/accessing_win ... ing_autofs

and just checkout automount (autofs) in general.

for fstab you may need the auto option added and the user option to allow the user to un/mount.

Boo

[Husse]

Well we blacklist ipv6 as it's hardly ever used and can cause (severe) problems
This indicates that "some network thing" is behaving a bit badly
We had in some previous versions fusesmb installed by default and that could have caused something like this
I can't find that in my logs (gnome though)

[Boo]

I have been checking my laptop logs and found that the ip6 module blacklist only shows up when my laptop was connected to a network via copper.
on a wireless network the blacklist ipv6 message does not show up.
I would check the other devices on your network and make sure they are not using (or probing for) some ipv6 related app/network protocol.
also check if you are using ipchains (and ipchains_ip6), there could something happening here too.

Boo

[Boo]

a quick fix might be to un-blacklist the ipv6 module.

edit /etc/modprobe.d/blacklist
and remove the line
blacklist ipv6

this will stop the warning messages but your NAS may still get woken up.

the fixed package in the bug report could be in the intrepid backport repository.
enable it and install the package

Boo

[Boo]

It would most likely be in the main jaunty repo.
the problem may be dependancies on the package, so one package may turn in lots...

Boo

[Husse]

In your case it seems to me that we have to find out what makes regular system or network calls
My logs reveal nothing of the kind - the only periodic log entry is the MARK entries in syslog every twenty minutes
I'm on gnome - could it be something in KDE 4? I don't really know what to search for here but something that happens regularly
Will reboot and check logs
Edit
Been in Felicia KDE RC1 for a while - nothing in the logs at a regular interval no ipv6 - what's going on in your end?

[Husse]

No I really don't know and I am grateful that you have this patience
I have all my facts here and there is no KDE on this machine (I think )

[Husse]

I have installed the latest Mint editions (and KDE a couple of times due to a bad DVD-RW)
I use Compatibility mode and what do I see rolling by on the screen?
kjournald commit interval 5 seconds
It could be ext3 itself that calls your NAS - journaling every 5 seconds....
A shot in the dark without a proposed solution