Beiträge von crusher606

crusher606 · 27. Februar 2021

Danke =)

Sehr cooler Hinweis !

Jetzt wo Du es mir gesagt hast, sehe und verstehe ich das die auto.mount gar nicht aufgerufen wird.

Die Funktion und den Inhalt der auto.config habe ich leider noch nicht ganz verstanden.

Wenn ich von automounts.xml auf auto.network wecheln möchte, dann könnte ich ja die "Auskommentierung" bei dem auto.mount Eintrag wegnehmen.

Dann wird die auto.master gelesen (darin der Pfad zum mounten und die mount-Datei (auto.network).

Muss ich die automounts.xml dann in der auto.config Datei irgendwo deaktivieren?

Oder wird eine der Mount-Arten vorrangig abgearbeitet ?

Es gibt auch Erfolge zu Berichten.

Ich habe jetzt alle meine NAS über die automounts.xml eingetragen und (nach einigen Korrekturen) auch alle Laufwerke unter "net" eingehängt gekomen =)

Das geht schon mal gut und vielleicht lasse ich das auch so.

Ich gehe davon aus, das ich im hdd/movie Verzeichnis noch eigene Ordnder mir Symlinks zu den NAS einfügen kann.
(das muss ich aber erst mal probieren)

Einige NAS (Netgear RND 2000) konnte ich einfach mit NFS einhängen

die älteren QNAP TS 209 gehen nur mit CIFS vers=1.0

und die neuen QNAP habe ich mit CIFS vers=2.0 eingehängt.

Somit habe ich eigentlich alles was ich brauche.

Testen muss ich aber mal, wie sich die mounts in der GigaBlue verhalten, wenn die NAS ausgeschaltet werden, oder in den Ruhemodus wechseln.

An dieser Stelle für heute erst mal vielen Dank für den Input und die Hilfe die NAS in mein TeamBlue 6.4 zu integrieren =)

crusher606 · 26. Februar 2021

Code

#
# A number of configuration options are not yet implemented:
#
# fully_qualified_hosts - not yet implemented.
#
# unmount_on_exit - since autofs always tries to re-connect
# to mounts left mounted from a previous shutdown this
# is a sensible option to implement and that will be
# done.
#
# exec_map_timeout - a timeout is not currently used for
# for program maps, might be implemented.
#
# tag - the tag option is not implemented within autofs.
#
#
# Supported options:
#
# arch, karch, os, osver - these options default to what is returned
# from uname(2) and can be overridden if required.
#
# full_os - has no default and must be set in the configuration
# if used in maps.
#
# cluster - if not set defaults to the host domain name. This option
# corresponds to the HP_UX cluster name (according to the amd
# source) and is probably not used in Linux but is set anyway.
#
# vendor - has a default value of "unknown", it must be set in the
# configuration if used in maps.
#
# auto_dir - is the base name of the mount tree used for external
# mounts that are sometimes needed by amd maps. Its default
# value is "/a".
#
# map_type - specifies the autofs map source, such as file, nis,
# ldap etc. and has no default value set.
#
# map_defaults - is used to override /defaults entries within maps
# and can be used to provide different defaults on specific
# machines without having to modify centrally managed maps.
# It is empty by default.
#
# search_path - colon seperated paths to search for maps that
# are not specified as a full path.
#
# dismount_interval - is equivalent to the autofs timeout option. It
# is only possible to use this with type "auto" mounts due
# to the way the autofs kernel module performs expiry. It
# takes its default value from the autofs internal default
# of 600 seconds.
#
# browsable_dirs - make map keys visible in directory listings.
# Note that support for the "fullybrowsable" option cannot
# be added using the existing kernel to user space autofs
# implementation.
#
# autofs_use_lofs - if set to "yes" autofs will attempt to use bind
# mounts for type "link" entries when possible.
#
# nis_domain - allows setting of a domain name other than the system
# default.
#
# local_domain - is used to override (or set) the host domain name.
#
# normalize_hostnames - if set to "yes" then the contents of ${rhost}
# is translated in its official host name.
#
# domain_strip - if set to "yes" the domain name part of the host
# is strippped when normalizing hostnames. This can be useful
# when using of the same maps in a multiple domain environment.
#
# normalize_slashes - is set to "yes" by default and will collapse
# multiple unescaped occurrences of "/" to a single "/".
#
# selectors_in_defaults, selectors_on_default - has a default value
# of "no". If set to "yes" then any defaults entry will be
# checked for selectors to determine the values to be used.
# selectors_in_defaults is the preferred option to use.
#
# ldap_base - has no default value. It must be set to the base dn
# that is used for queries if ldap is to be used as a map
# source.
#
# ldap_hostports - has no default value set. It must be set to
# the URI of the LDAP server to be used for lookups when
# ldap is used a map source. It may contain a comma or
# space seperated list of LDAP URIs.
#
# hesiod_base - the base name used for hesiod map sources.
#
# Additional configuration options added:
#
# linux_ufs_mount_type - set the default system filesystem type that's
# used for mount type ufs. There's no simple way to determine
# what the system default filesystem is and am-utils needs to
# be continually updated to do this and can easily get it wrong
# anyway.
#
#
# Define global options for the amd parser within autofs.
#
[ amd ]
#
# Override the internal default with the same timeout that
# is used by the override in the autofs configuration, sanity
# only change.
#
dismount_interval = 300
#
# map_type = file
#
# Overriding this can cause autofs to use less resources because
# it will use symlinks instead of bind mounts in certain cases.
# You should ensure that the autofs kernel module your using
# supports expration of symlinks for best results (although this
# appears to work reasonably well most of the time without the
# update).
#
# autofs_use_lofs = yes
#
# Several configuration options can be set per mount point.
# In particulr map_type, map_name, map_defaults, search_path,
# browsable_dirs, dismount_interval and selectors_in_defaults
# (not all of which are currently implemented, see above).
#
# Also, if a section for an amd mount point is defined here
# it isn't necessary to specify the format in the corresponding
# master map entry and the format will be inherited for type
# "auto" mounts.
#
# [ /expamle/mount ]
# dismount_interval = 60
# map_type = nis

Alles anzeigen

crusher606 · 26. Februar 2021

Hallo Günther,

ich kann die auto.conf nicht hier posten, da die Datei mehr als 10.000 Zeichen hat.

(ich versuche die mal in zwei Teilen zu posten . . . . )

Code

#
# Define default options for autofs.
#
[ autofs ]
#
# master_map_name - default map name for the master map.
#
#master_map_name = auto.master
#
# timeout - set the default mount timeout in secons. The internal
# program default is 10 minutes, but the default installed
# configuration overrides this and sets the timeout to 5
# minutes to be consistent with earlier autofs releases.
#
timeout = 300
#
# master_wait - set the default maximum time to wait for the
# master map to become available if it cannot
# be read at program start (default 10, wait
# for 10 seconds then continue).
#
# master_wait = 10
#
# negative_timeout - set the default negative timeout for
# failed mount attempts (default 60).
#
#negative_timeout = 60
#
# mount_wait - time to wait for a response from mount(8).
# Setting this timeout can cause problems when
# mount would otherwise wait for a server that
# is temporarily unavailable, such as when it's
# restarting. The default setting (-1) of waiting
# for mount(8) usually results in a wait of around
# 3 minutes.
#
#mount_wait = -1
#
# umount_wait - time to wait for a response from umount(8).
#
#umount_wait = 12
#
# browse_mode - maps are browsable by default.
#
browse_mode = no
#
# mount_nfs_default_protocol - set the default protocol that mount.nfs(8)
# uses when performing a mount. Autofs needs
# to know the default NFS protocol that
# mount.nfs(8) uses so it can do special case
# handling for its availability probe for
# different NFS protocols. Since we can't
# identify the default automatically we need
# to set it in our configuration.
#
#mount_nfs_default_protocol = 3
#
# append_options - append to global options instead of replace.
#
#append_options = yes
#
# logging - set default log level "none", "verbose" or "debug"
#
#logging = none
#
# force_standard_program_map_env - disable the use of the "AUTOFS_"
# prefix for standard environemt variables when
# executing a program map. Since program maps
# are run as the privileded user this opens
# automount(8) to potential user privilege
# escalation when the program map is written
# in a language that can load components from,
# for example, a user home directory.
#
# force_standard_program_map_env = no
#
# use_mount_request_log_id - Set whether to use a mount request log
# id so that log entries for specific mount
# requests can be easily identified in logs
# that have multiple conncurrent requests.
#
#use_mount_request_log_id = no
#
# Define base dn for map dn lookup.
#
# Define server URIs
#
# ldap_uri - space seperated list of server uris of the form
# <proto>://<server>[/] where <proto> can be ldap
# or ldaps. The option can be given multiple times.
# Map entries that include a server name override
# this option.
#
# This configuration option can also be used to
# request autofs lookup SRV RRs for a domain of
# the form <proto>:///[<domain dn>]. Note that a
# trailing "/" is not allowed when using this form.
# If the domain dn is not specified the dns domain
# name (if any) is used to construct the domain dn
# for the SRV RR lookup. The server list returned
# from an SRV RR lookup is refreshed according to
# the minimum ttl found in the SRV RR records or
# after one hour, whichever is less.
#
#ldap_uri = ""
#
# ldap_timeout - timeout value for the synchronous API calls
# (default is LDAP library default).
#
#ldap_timeout = -1
#
# ldap_network_timeout - set the network response timeout (default 8).
#
#ldap_network_timeout = 8
#
# search_base - base dn to use for searching for map search dn.
# Multiple entries can be given and they are checked
# in the order they occur here.
#
#search_base = ""
#
# Define the LDAP schema to used for lookups
#
# If no schema is set autofs will check each of the schemas
# below in the order given to try and locate an appropriate
# basdn for lookups. If you want to minimize the number of
# queries to the server set the values here.
#
#map_object_class = nisMap
#entry_object_class = nisObject
#map_attribute = nisMapName
#entry_attribute = cn
#value_attribute= nisMapEntry
#
# Other common LDAP naming
#
#map_object_class = automountMap
#entry_object_class = automount
#map_attribute = ou
#entry_attribute = cn
#value_attribute= automountInformation
#
#map_object_class = automountMap
#entry_object_class = automount
#map_attribute = automountMapName
#entry_attribute = automountKey
#value_attribute= automountInformation
#
# auth_conf_file - set the default location for the SASL
# authentication configuration file.
#
#auth_conf_file = /etc/autofs_ldap_auth.conf
#
# map_hash_table_size - set the map cache hash table size.
# Should be a power of 2 with a ratio of
# close to 1:8 for acceptable performance
# with maps up to around 8000 entries.
# See autofs.conf(5) for more details.
#
#map_hash_table_size = 1024
#
# use_hostname_for_mounts - nfs mounts where the host name resolves
# to more than one IP address normally need
# to use the IP address to esure a mount to
# a host that isn't responding isn't done.
# If that behaviour is not wanted then set
# ths to "yes", default is "no".
#
#use_hostname_for_mounts = "no"
#
# disable_not_found_message - The original request to add this log message
# needed it to be unconditional. That produces, IMHO,
# unnecessary noise in the log so a configuration option
# has been added to provide the ability to turn it off.
# The default is "no" to maintain the current behaviour.
#
#disable_not_found_message = "no"
#
# sss_master_map_wait - When sssd is starting up it can sometimes return
# "no such entry" for a short time until it has read
# in the LDAP map information. Internal default is 0
# seconds, don't wait but if there is a problem with
# autofs not finding the master map at startup (when
# it should) then try setting this to 10 to work
# around it.
#
#sss_master_map_wait = 0
#
# Options for the amd parser within autofs.
#
# amd configuration options that are aren't used, haven't been
# implemented or have different behaviour within autofs.
#
# A number of the amd configuration options are not used by autofs,
# some because they are not relevant within autofs, some because
# they are done differently in autofs and others that are not yet
# implemented.
#
# Since "mount_type" is always autofs (because there's no user space
# NFS server) the configuration entries relating to that aren't used.
# Also, server availability is done differently within autofs so the
# options that relate to the amd server monitoring sub-system are
# also not used.
#
# These options are mount_type, auto_attrcache, portmap_program,
# nfs_vers_ping, nfs_allow_any_interface, nfs_allow_insecure_port,
# nfs_proto, nfs_retransmit_counter, nfs_retransmit_counter_udp,
# nfs_retransmit_counter_tcp, nfs_retransmit_counter_toplvl,
# nfs_retry_interval, nfs_retry_interval_udp, nfs_retry_interval_tcp,
# nfs_retry_interval_toplvl and nfs_vers.
#
#
# Other options that are not used within the autofs implementation:
#
# log_file, truncate_log - autofs used either stderr when running in
# the foreground or sends its output to syslog so an alternate
# log file (or truncating the log) can't be used.
#
# print_pid - there's no corresponding option for this within autofs.
#
# use_tcpwrappers, show_statfs_entries - there's no user space NFS
# server to control access to so this option isn't relevant.
# The show_statfs_entries can't be implemented for the same
# reason.
#
# debug_mtab_file - there's no user space NFS server and autofs
# avoids using file based mtab whenever possible.
#
# sun_map_syntax - obviously, are provided by autofs itself.
#
# plock, show_statfs_entries, preferred_amq_port - not supported.
#
# ldap_cache_maxmem, ldap_cache_seconds - external ldap caching
# is not used by autofs.
#
# ldap_proto_version - autofs always attempts to use the highest
# available ldap protocol version.
#
# cache_duration, map_reload_interval, map_options - the map
# entry cache is continually updated and stale entries
# cleaned on re-load, which is done when map changes are
# detected so these configuration entries are not used
# by autofs.
#
# localhost_address - is not used within autofs. This
# configuration option was only used in the amd user
# space server code and is not relevant within autofs.
#
#
# Options that are handled differently within autofs:
#
# pid_file - must be given as a command line option on startup.
#
# print_version - program version and feature information is obtained
# by using the automount command line option "-V".
#
# debug_options, log_options - autofs has somewhat more limited
# logging and debug logging options. When the log_options
# options is encountered it is converted to the nearest
# matching autofs logging option. Since the configuration
# option debug_options would be handled the same way it
# is ignored.
#
# restart_mounts - has no sensible meaning within autofs because autofs
# always tries to re-connect to existing mounts. While this
# has its own set of problems not re-connecting to existing
# mounts always results in a non-functional automount tree if
# mounts were busy at the last shutdown (as is also the case
# with amd when using mount_type autofs).
#
# forced_unmounts - detaching mounts often causes serious problems
# for users of existing mounts. It is used by autofs in some
# cases, either at the explicit request of the user (with a
# command line or init option) and in some special cases during
# program operation but is avoided whenever possible.
#

Alles anzeigen

crusher606 · 26. Februar 2021

Danke Uwe für diese Info.
Ich hänge die ganzen NAS mal per automounts.xlm ein und probiere das mal.

Ich hatte halt Bedenken das beim Starten erst 10 x der TimeOut kommen muss, weil alle NAS aus sind.

crusher606 · 26. Februar 2021

Ich glaube mich zu erinnern.....

Mit autofs werden die mounts bei Bedarf eingehängt, wenn man auf den Symlink geht.
Es wird beim booten nicht sofort versucht auf den mount zuzugreifen.

Das führt im Vergleich zur automounts.xlm Variante zu boot-verzögerungen, wenn ein Laufwerk eingehängt werden soll,

das garnicht angeschaltet ist.

(So war das und ist das zumindest bei meiner VU+ mit VTi, wenn ich das hier erwähnen darf)

crusher606 · 26. Februar 2021

???? Die auto.mount ist nie beteiligt ?? Ne, oder ?

Da MUSS man dann alles in die automounts.xml eintragen?

Das ist aber nicht schön.

Meine auto.config kann ich nicht eintragen, die ist zu lang (mehr als 10.000 Zeichen . . .
Da ist auch nicht viel aktiv.

crusher606 · 26. Februar 2021

Ja, der GB habe ich über setpasswd ein neues gegeben, aber das brauche ich doch nicht,

da ich nur auf externe Netzlaufwerke (NAS) zugreife.

In der auto.master steht:

Code

/media/autofs /etc/auto.network --ghost

und über diese Zeile in der auto.mount sollte das NAS eigentlich in dem Ordner landen.

Code

QNAP40 -fstype=cifs,vers=2.0,rw,username=user1,password=passwort1 ://192.168.178.40/Qrecordings/movie

was ist daran falsch ?

Muss man die automount.xml löschen, damit beim Start der Box das autofs über die auto.master gelesen wird ?

Das ist alles sehr seltsam.

crusher606 · 26. Februar 2021

Erst mal ein nettes Hallo an alle,

ich würde gerne meine NAS (mehrere) aus meinem Netzwerk mit in die GigaBlue UHD Quad 4K mit TeamBlue 6.4 einhängen und verstehe das Vorgehen bei der GigaBLue aber wohl nicht.

Die NAS über den Freigabemanager per NFS und CIFS einzuhängen bekomme ich ja hin. (Die Einräge landen ja in der automount.xml)

Ich editiere auch die automount.xml und schreibe da alle NAS rein die ich habe, aber eigentlich will ich das so nicht haben.

Teils mit NFS, teils mit CIFS.

Das will ich aber eigenlich so nicht haben.....

Ich habe auch noch eine VU+DUO 4K bei der ich die Fraigaben über die auto.network eingetragen habe. (die auto.master verweist auf die auto.network)

Die Laufwerke werden dann unter media/net eingehängt

Dann habe ich im Aufnahmeverzeichnis auf der internen Festplatte eigene Ordner für die NAS erstellt und in diesen Ordnern je einen Symlink auf die entsprechende Fraigabe gesetzt.

(Das hat den Vorteil das ausgeschlatete NAS nicht den Start der Box verzögern, weil eine NAS nicht an ist.)

Das ich diese beiden Dateien der VU+ mit VTi aber nicht 1:1 für die GigaBlue TeamBlue nehmen kann habe ich schon gemerkt.

Da tat sich nach dem Neustart der Box nix. Keine NAS eingehängt.

Ich bekomme es einfach nicht hin, das ich einen Eintrag in die auto.network eintrage, der dann auch unter media/net gemountet wird, so wie es in der auto.master drin steht.

Hat jemand die Nerven mir zu zeigen wo der Haken ist ?
Kann das TeamBlue eigentlich überhaupt mit autofs umgehen ?

Code

# automounter configuration
#-------------------------------
# For CIFS shares:
#
# mntpoint -fstype=cifs,vers=2.0,rw,username=myuser,password=mypass ://IP_or_example.com/sharename
QNAP40 -fstype=cifs,vers=2.0,rw,username=user1,password=passwort1 ://192.168.178.40/Qrecordings/movie
QNAP41 -fstype=cifs,vers=2.0,rw,username=user2,password=passwort2 ://192.168.178.41/Qrecordings
QNAP42 -fstype=cifs,vers=2.0,rw,username=user3,password=passwort3 ://192.168.178.42/Qrecordings
QNAP50 -fstype=cifs,vers=2.0,rw,username=user4,password=passwort4 ://192.168.178.50/Movie
VUduo2 -fstype=cifs,vers=2.0,rw,username=admin,password= ://192.168.178.100/Harddisk/movie
#
#-------------------------------
# For NFS shares:
#
# mntpoint -fstype=nfs,rw,retry=0 192.168.1.101:/sharename
#
# use "retry=0" to prevent client waiting (timeout=60 sec) for unreliable servers.
#NFS
NAS20 -fstype=nfs,rw,retry=0 192.168.178.20:/media/music
NAS21 -fstype=nfs,rw,retry=0 192.168.178.21:/media
NAS22 -fstype=nfs,rw,retry=0 192.168.178.22:/media
NAS23 -fstype=nfs,rw,retry=0 192.168.178.23:/media
NAS24 -fstype=nfs,rw,retry=0 192.168.178.24:/media
#
#-------------------------------

Alles anzeigen

Beiträge von crusher606

[erledigt] Leider schon wieder Netzwerk Frage für NAS

[erledigt] Leider schon wieder Netzwerk Frage für NAS

[erledigt] Leider schon wieder Netzwerk Frage für NAS

[erledigt] Leider schon wieder Netzwerk Frage für NAS

[erledigt] Leider schon wieder Netzwerk Frage für NAS

[erledigt] Leider schon wieder Netzwerk Frage für NAS

[erledigt] Leider schon wieder Netzwerk Frage für NAS

[erledigt] Leider schon wieder Netzwerk Frage für NAS