search for: mount_data

....fr> --- usr/kinit/nfsmount/main.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/usr/kinit/nfsmount/main.c b/usr/kinit/nfsmount/main.c index 36b29a5f..cca9e4ec 100644 --- a/usr/kinit/nfsmount/main.c +++ b/usr/kinit/nfsmount/main.c @@ -36,12 +36,15 @@ static struct nfs_mount_data mount_data = { }; int nfs_port; +int nfs_version; static struct int_opts { char *name; int *val; } int_opts[] = { {"port", &nfs_port}, + {"nfsvers", &nfs_version}, + {"vers", &nfs_version}, {"rsize", &mount_data.rsize}, {&quo...

...g.uk> --- usr/kinit/nfsmount/main.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/usr/kinit/nfsmount/main.c b/usr/kinit/nfsmount/main.c index 36b29a5..cca9e4e 100644 --- a/usr/kinit/nfsmount/main.c +++ b/usr/kinit/nfsmount/main.c @@ -36,12 +36,15 @@ static struct nfs_mount_data mount_data = { }; int nfs_port; +int nfs_version; static struct int_opts { char *name; int *val; } int_opts[] = { {"port", &nfs_port}, + {"nfsvers", &nfs_version}, + {"vers", &nfs_version}, {"rsize", &mount_data.rsize}, {&quo...

...ownloads I get to following error message mount: wrong fs type, bad option, bad superblock on //esotericVAIO/Downloads, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so I see the following error message in dmesg smbfs: mount_data version 1919251317 is not supported What does the dmesg mean? Thanks for your time. Chuck Downing Leadville, Colorado, USA

...tOS 4.5 box running stock kernel etc - I have tried using cifs and also smbfs My fstab looks like //share/name /mount/point smbfs username=user,password=password,uid=useridhere 0 0 or the same using cifs When i try and mount that i get the following errors depending on the share type smbfs: mount_data version 1919251317 is not supported CIFS VFS: cifs_mount failed w/return code = -22 i would have thought that cifs was the way forward but any ideas? These use creds are being used on an ancient 7.3 box and they work fine thanks

...ed options via the kernel cmdline. Everyone else prefers probably the fast mount. The defaults should look more like that: --- nfsmount/main.c~ 2004-02-12 03:19:14.000000000 +0100 +++ nfsmount/main.c 2004-05-27 13:31:19.000000000 +0200 @@ -20,9 +20,9 @@ static char *progname; static struct nfs_mount_data mount_data = { .version = NFS_MOUNT_VERSION, - .flags = NFS_MOUNT_NONLM, - .rsize = 1024, - .wsize = 1024, + .flags = NFS_MOUNT_NONLM | NFS_MOUNT_VER3 | NFS_MOUNT_TCP, + .rsize = 8192, + .wsize = 8192, .timeo = 7, .retrans = 3, .acregmin = 3, -- USB is for mice, FireWire is for men! sUse...

Hi, I am using linux 2.4.2 with smb 2.0.7.5. Since a few days, my smbmount of NT 2000 or W98 are refused with a message: mount_data version 1919251317 is not supported A few searches showed only an old message of mid-summer last year. Why is it showing up now and how can I get my mounts back? Thanks, Yves

Creates an additional LV, CoreDump. This LV, if present, is mounted at /var/log/core. Its default size is 10240 MB (10G) and has a minimum size of 1024 MB. Additionally, the default log partition size was changed from 256 MB to 2048 MB (2G). Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-storage | 23 ++++++++++++++++++----- scripts/ovirt-early

...ibc] nfsmount: Use kernel client's default value for timeo option The current default of timeo=7 (0.7 seconds) is too short, especially on slow networks. We should not override the kernel client's default unless explicitly requested. This option is passed to the kernel through struct nfs_mount_data rather than as a string, so we have to provide some value. The kernel client currently treats either 0 or UINT_MAX as requesting the default. nfs-utils passes 0, so do the same here. Reported-by: Alkis Georgopoulos <alkisg at gmail.com> References: https://lists.zytor.com/archives/klibc/201...

...d be removed, and the nls_utf8 abuse :) Also, it now uses an ioctl to set the codepages to use (borrowed from the work by Artem V. Ryabov). This allows you to mount a modified smbfs with an unmodified smbmount or vice versa and that should give less "version support" than my old modified mount_data variant. One thing that has been removed is the support for a "default mapping", this means that the patched version should behave like an unpatched version until you ioctl it. Patch at: http://www.hojdpunkten.ac.se/054/samba/smbfs-nls-2.2.16-pre2.patch This also needs a small change...

Hi, I'm resending since I got no feedback: I assume that the message was lost... The attached patch fixes a few bugs related to the spoofing portmapper used by nfsmount. Regards, Louis -- Dr Louis Rilling Kerlabs Skype: louis.rilling Batiment Germanium Phone: (+33|0) 6 80 89 08 23 80 avenue des Buttes de Coesmes http://www.kerlabs.com/ 35700 Rennes -------------- next part

...ot; - vgcreate /dev/HostVG "${partpv}" + vgcreate /dev/HostVG "${physical_vols}" if [ "$SWAP_SIZE" -gt 0 ]; then log "Creating swap partition" @@ -665,9 +727,75 @@ create_hostvg() log "Mounting data partition" mount_data fi - log "Completed!" + log "Completed HostVG!" + +} + +create_appvg() +{ + log "Creating LVM partition(s) for AppVG" + local drv= + for drv in $APPVGDRIVE; do + wipe_partitions "$drv" + reread_partitions "$drv" +...

...os.system("plymouth --quit") + unmount_logging_services() + + ret = os.system("umount /var/log") + if ret > 0: + return ret + for srv in logging_services: + os.system("service %s start") % srv + return + +# mount data partition +def mount_data(): + if os.path.ismount("/data"): + return + + if os.path.exists("/dev/HostVG/Data"): + os.system("mkdir -p /data") + os.system("mount /data") + os.system("mkdir -p /data/images") + os.system("mkdir -p /...