search for: root_squashed

Hi Samba, I hope you are doing well. I run a cifs / nfs CTDB clustered NAS solution, and I find that when I reboot any of the nodes in the cluster, I must re-export the nfs mounts so they show up properly. Perhaps this is a general linux nfs bug and I am barking up the wrong tree, but I haven't found any problem / solution mentioning this as of yet besides my own known workaround

On 04/12/2016 10:58 AM, TomK wrote: > Hey Martin, > > Thanks very much. Appreciate you jumping in on this thread. Can you provide some more details with respect to which libvirt version you have installed. I know I've made changes in this space in more recent versions (not the most recent). I'm no root_squash expert, but I was the last to change things in the space so that

On Mon, Apr 11, 2016 at 08:02:04PM -0400, TomK wrote: >Hey All, > >Wondering if anyone had any suggestions on this topic? > The only thing I can come up with is: '/var/lib/one//datastores/0/38/disk.1': Permission denied ... that don't have access to that file. Could you elaborate on that? I think it's either: a) you are running the domain as root or b) we

.... My test case is : root at wagram:~# swaks --to tstifi04 --server imap --protocol lmtp --header-X-Spam-Status yes root at wagram:~# (imap VM LMTP proxies to telegraphe5 VM in this test) mbox folders are in users homedir, no generic "vmail" unix account. Real posixAccounts in LDAP, NFS root_squashed. sieve "fileinto "Junk" call goes wrong : > Feb? 6 17:56:03 telegraphe5 dovecot: lmtp(tstifi04): Error: > PytSHqIRW1x2dgAA+Fldtw: sieve: msgid=unspecified: failed to store into > mailbox 'Junk': Read-only mbox straced : https://pastebin.com/A53hDYnS I may miss s...

Hello all. I converted my server from Fedora Core 3 to CentOS 4.1 and I've been slogging unsuccessfully through an NFSv4 problem. I'm using the same configuration for NFS that I had in place on FC3 that worked. On the server, I have the following data structure: /data /data/archive /data/pictures /data/music Each is a separate ext3 filesystem mounted with rw,acl. /etc/exports

Hey John, Hehe, I got the right guy then. Very nice! And very good ideas but I may need more time to reread and try them out later tonight. I'm fully in agreement about providing more details. Can't be accurate in a diagnosis if there isn't much data to go on. This pool option is new to me. Please tell me more on it. Can't find it in the file below but maybe it's

[ I would be way easier to reply if you didn't top-post ] On Tue, Apr 12, 2016 at 12:07:50PM -0400, TomK wrote: >Hey John, > >Hehe, I got the right guy then. Very nice! And very good ideas but I >may need more time to reread and try them out later tonight. I'm fully >in agreement about providing more details. Can't be accurate in a >diagnosis if there isn't

On 04/12/2016 03:55 PM, TomK wrote: > > On 4/12/2016 3:40 PM, Martin Kletzander wrote: >> [ I would be way easier to reply if you didn't top-post ] >> >> On Tue, Apr 12, 2016 at 12:07:50PM -0400, TomK wrote: >>> Hey John, >>> >>> Hehe, I got the right guy then. Very nice! And very good ideas but I >>> may need more time to reread

Hai, A quick reply, Since there is a major traffic jam here, still at the office, but its resolving now.. > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Gaiarin via samba > Verzonden: maandag 29 oktober 2018 17:33 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Again NFSv4 and Kerberos at the 'samba

Fedora 13 is using nfs4, and there is a problem in opening files requiring OpenOffice if accessed over an nfs3 mount, so it's time to change. I found a couple of tutorials, and got it *almost* working correctly. This is where I need help. Logwatch tells me /nfs4exports/Data1 and /Data1 have same filehandle for *,192.168.0.0/24,192.168.0.0/255.255.255.0, using first The tutorial I was

I have been running a local repository on a CentOS4 server. It serves CentOS4 clients (and FC5, FC6, and SuSE10.x if I bother to mention). My current options for exports is (ro,wdelay,insecure,root_squash). The ro and insecure options were added manually and others are default. I understand 'sync' is the default although it is not shown by exportfs -v. I also found this description in

Adding in libvir-list. Cheers, Tom K. ------------------------------------------------------------------------------------- Mobile: 416 618 8456 Home: 905 857 9652 Living on earth is expensive, but it includes a free trip around the sun. On 4/7/2016 7:32 PM, TomK wrote: > Hey All, > > I've an issue where libvirtd tries to access an NFS mount but errors > out with: can't

On 4/12/2016 5:08 PM, John Ferlan wrote: > > On 04/12/2016 03:55 PM, TomK wrote: >> On 4/12/2016 3:40 PM, Martin Kletzander wrote: >>> [ I would be way easier to reply if you didn't top-post ] >>> >>> On Tue, Apr 12, 2016 at 12:07:50PM -0400, TomK wrote: >>>> Hey John, >>>> >>>> Hehe, I got the right guy then. Very

My old nfs server was an old dual Xeon machine running debian. Everything worked fine. Then I switched over to a new Penguin Computer Altus 2600 (if Im not mistaken) with two Dual-Core AMD Opteron(tm) Processor 2210 and 4GB of ram. CentOS4.4 is running on it. Now here is the thing, this nfs server is exporting "/home" and all workstations mount the /home dir via fstab. Ever since I

Howdy, With 3.1.3 the option was added to disable the builtin Gluster NFS. Does that mean that the following scenario should work: 1. Disable Gluster NFS "gluster volume set <VOLUME> nfs.disable on" 2. Restart the gluster servers for good measure 3. On one of the gluster servers, mount the volume using the gluster fuse client: mkdir /export/users # In /etc/fstab add

We have been experiencing a debilitating 'bug' in samba where something is causing a flood of the messages seen below in smbstatus and the network drives ( in our case N: ) on all clients become unresponsive. In fact, the entire client becomes unresponsive, essentially making them unusable until samba is restarted. We first saw this and connected it to the following open bug in samba

On Tue, Apr 07, 2020 at 02:33:20PM +0200, Pino Toscano wrote: > On Tuesday, 7 April 2020 14:18:47 CEST Richard W.M. Jones wrote: > > On Tue, Apr 07, 2020 at 01:25:02PM +0200, Pino Toscano wrote: > > > The important thing is still that that you need to have space for the > > > temporary files somewhere: be it /var/tmp, /mnt/scratch, whatever. > > > Because of

Hai Marco, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Gaiarin via samba > Verzonden: vrijdag 26 oktober 2018 11:23 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Again NFSv4 and Kerberos at the 'samba way'... > > Mandi! L.P.H. van Belle via samba > In chel di` si favelave... > >

On Wednesday, 10 June 2020 12:31:33 CEST Richard W.M. Jones wrote: > I finally got access to the container. This is how it's configured: > > * / => an overlay fs. > > There is sufficient space here, and there are no "funny" restrictions, > to be able to create the libguestfs appliance. I proved this by > setting TMPDIR to a temporary directory under / and

Hi everyone, If a VM is configured to have a console attached to it, like using http://libvirt.org/formatdomain.html#elementCharConsole Libvirt offers access to VM serial console's using the virDomainOpenConsole API[1] However, I didn't find a way to 1. list the existing connections to the console 2. kill an existing connection - without reconnecting using VIR_DOMAIN_CONSOLE_FORCE[2]