Displaying 20 results from an estimated 1100 matches similar to: "Disk full / file corrupted"
2011 Apr 07
1
Hidden files
Dear All!
Does anyone have troubles with setting hidden attribute?
Read-only set and unset properly
Hindden - can't set at all
mount:
/mnt/disk.img on /drv1 type ext4
(rw,noexec,nosuid,nodev,loop=/dev/loop0,acl,user_xattr)
Samba 3.5.8
smb.conf
----------------------------
[global]
pid directory = /opt/samba/run
lock directory = /opt/samba/cache
private dir = /opt/samba/cache
log file =
2007 Aug 28
1
PV domain on NAS
Hi All,
Could anybody tell me the creating of pv domain on nas. I mean to say that
root file sytem should be at nas location.
Useful links will be most welcome.
Thanks,
Trilok
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2019 Jan 23
2
can't write Samba share as anonymous
Hello,
I'm trying to access a Samba share as anonymous/guest user, so I have
added the following entry inf file smb.conf (Samba 4.9)
guest account = andrea
map to guest = bad user
...
[test]
available = yes
browsable = yes
guest ok = yes
nfs4: acedup = merge
nfs4: mode = special
path = /var/tmp/test
read only = no
and the shared directory /var/tmp/test has the following permission (so
2013 Jul 04
1
Failed to create SR with lvmoiscsi on xcp1.6[ [opterr=Logical Volume partition creation error [opterr=error is 5]]
Hello Experts,
When I try to create SR with lvm over iSCSI, it always failed, I list my xe command and debug info:
[root@xcp16 log]# xe sr-create host-uuid=a226200e-f7ff-4dee-b679-e5f114d1e465 content-type=user name-label=shared_disk_sr shared=true device-config:target=192.168.1.2 device-config:targetIQN=iqn.2013-07.example:shareddisk device-config:SCSIid=1IET_00010001 type=lvmoiscsi
The SR is
2001 May 23
2
ext3 message if FS is not ext3
Hi,
i think this message should be removed ;)
paradigm:~# umount /mnt2
paradigm:~# mkdosfs /dev/fd0
mkdosfs 2.5 (07 Jan 2000)
paradigm:~# /tmp/syslinux /dev/fd0
paradigm:~# sync
paradigm:~# mount /dev/fd0 /mnt2
VFS: Can't find an ext3 filesystem on dev fd(2,0).
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense"
2013 May 12
2
Reinstalling boot blocks on a ZFS-only system
So, I've long known and it makes sense that when you're booted from a ZFS volume, you can't mess with the boot-loader. And, I know a few months ago I had a set of commands I would use when booted from a CD that would initialize the network and copy the "release/boot" from somewhere else so that I could install bootblocks and boot-loaders from more recent code. Sadly, I
2004 Dec 01
2
cp --o_direct
Another question.
When my database is running, I do
[oracle@LNCSTRTLDB03 LPTE3]$ cp --o_direct xdb01.dbf /tmp
cp: cannot open `xdb01.dbf' for reading: Permission denied
[oracle@LNCSTRTLDB03 LPTE3]$
When the database is shudown it works.
Is this normal for ocfs because with any other filesystem I can just
copy a file at any time (Its only a testing, I know I cant copy
datafiles and have
2013 Jun 30
1
why check f_path.mnt is equal for source and dest in btrfs_ioctl_clone()?
This gives EXDEV for clone operations that btrfs could otherwise execute
and with slight change of circumstances will actually execute fine.
Imagine we have a btrfs on /dev/mapper/foobar with subvols /foo and
/bar. Let’s also imagine top of said fs in mounted at /mnt. In this
case, a cross-subvol clone of /mnt/foo/srcfile to /mnt/bar/dstfile will
succeed.
However, if only the individual
2014 Jan 20
2
newlines with write-append
Silly bash scripts have stuff like below to get things done, but equally
silly guestfish scripts fail to add the required newline. Why is that?
echo "$dev1 $mnt1 $fs $opts 1 2" >> /etc/fstab
echo "$dev2 $mnt2 $fs $opts 1 2" >> /etc/fstab
write-append /etc/fstab "$dev1 $mnt1 $fs $opts 1 2" : \
write-append /etc/fstab "$dev2 $mnt2 $fs $opts 1 2"
2017 Dec 29
2
"file changed as we read it" message during tar file creation on GlusterFS
Hi Mauro,
What version of Gluster are you running and what is your volume
configuration?
IIRC, this was seen because of mismatches in the ctime returned to the
client. I don't think there were issues with the files but I will leave it
to Ravi and Raghavendra to comment.
Regards,
Nithya
On 29 December 2017 at 04:10, Mauro Tridici <mauro.tridici at cmcc.it> wrote:
>
> Hi All,
2009 May 27
1
Clustering dovecot?
Currently I have a mail server running postfix and dovecot with users
in mysql. I have Outlook (blich) clients checking IMAP mail on the
server. I'd like to build some fault-tolerance into that system in
case I have hardware failure.
I've read through: http://wiki.dovecot.org/MailLocation/SharedDisk
but I feel I need more information. My basic understanding is that
I'll need 2
2018 Jan 02
2
"file changed as we read it" message during tar file creation on GlusterFS
Hi All,
any news about this issue?
Can I ignore this kind of error message or I have to do something to correct it?
Thank you in advance and sorry for my insistence.
Regards,
Mauro
> Il giorno 29 dic 2017, alle ore 11:45, Mauro Tridici <mauro.tridici at cmcc.it> ha scritto:
>
>
> Hi Nithya,
>
> thank you very much for your support and sorry for the late.
> Below
2011 Dec 09
1
Samba + acl,user_xattr
Hello All!
Can't make Samba use acl and extended user attributes to save DOS file
attributes.
Please, help me configure properly.
My steps on Windows XP:
1 - Open share
2 - Open property of file 1122/22.bmp
3 - Check file attribute: hidden
4 - Click Apply
5 - Click Close
6 - Open property again
7 - Attribute Hidden not checked.
Samba dont save attributes!!!
getfattr -d
2017 May 05
10
[Bug 12769] New: error allocating core memory buffers (code 22) depending on source file system
https://bugzilla.samba.org/show_bug.cgi?id=12769
Bug ID: 12769
Summary: error allocating core memory buffers (code 22)
depending on source file system
Product: rsync
Version: 3.1.0
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
2017 Dec 29
0
"file changed as we read it" message during tar file creation on GlusterFS
Hi Nithya,
thank you very much for your support and sorry for the late.
Below you can find the output of ?gluster volume info tier2? command and the gluster software stack version:
gluster volume info
Volume Name: tier2
Type: Distributed-Disperse
Volume ID: a28d88c5-3295-4e35-98d4-210b3af9358c
Status: Started
Snapshot Count: 0
Number of Bricks: 6 x (4 + 2) = 36
Transport-type: tcp
Bricks:
2018 Jan 02
0
"file changed as we read it" message during tar file creation on GlusterFS
I think it is safe to ignore it. The problem exists? due to the minor
difference in file time stamps in the backend bricks of the same sub
volume (for a given file) and during the course of tar, the timestamp
can be served from different bricks causing it to complain . The ctime
xlator[1] feature once ready should fix this issue by storing time
stamps as xattrs on the bricks. i.e. all bricks
2018 Jan 02
1
"file changed as we read it" message during tar file creation on GlusterFS
Hi Ravi,
thank you very much for your support and explanation.
If I understand, the ctime xlator feature is not present in the current gluster package but it will be in the future release, right?
Thank you again,
Mauro
> Il giorno 02 gen 2018, alle ore 12:53, Ravishankar N <ravishankar at redhat.com> ha scritto:
>
> I think it is safe to ignore it. The problem exists due to the
2011 Apr 25
0
dovecot & OCFS2 Cluster
Am 25.04.2011 19:02, schrieb Osvaldo Alvarez Pozo:
> hi all
>
> We have an ocfs2 cluster compose of 4 Debian lenny serveurs wich have
> access to an ISCSI LUN we have create a partition on this Lun and
> formated this partition as OCFS2.
> 2 serveurs does mail delivery (SMTP) and the two other are pop/imap
> servers. The smtp servers use dovecot LDA to deliver to mailboxes.
2023 Apr 02
0
samba Digest, Vol 244, Issue 2
On 01-04-2023 20:38, Rowland Penny via samba wrote:
>
>
> On 01/04/2023 19:10, Gary Dale via samba wrote:
>
>
>> I tried using Samba once rather than NFS but that broke things. I
keep my mail on the server and Thunderbird didn't work properly.
Reverting to NFS fixed that. Also, Samba shares seemed slower and less
reliable. NFS just works.
>
> I use
2023 Apr 03
0
clients not connecting to samba shares
I messed up the subject line. I was so sure that I had taken care of it.
Oh well...
For documentation purposes, I resend this e-mail so that it appears in
the correct thread. Sorry for the noise.
On 01-04-2023 20:38, Rowland Penny via samba wrote:
>
>
> On 01/04/2023 19:10, Gary Dale via samba wrote:
>
>
>> I tried using Samba once rather than NFS but that broke things.