search for: filesysems

I''m observing the following behavior in our environment (Sol10U2, E2900, 24x96, 2x2Gbps, ...) - I''ve a compressed ZFS filesystem where I''m creating a large tar file. I notice that the tar process is running fine (accumulating CPU, truss shows writes, ...) but for whatever reason the timestamp on the file doesn''t change nor does the file size change. The same is

Hi In our office environment few servers mostly database servers and yesterday it happened for one application server(first time) the partion is getting "read only". I was checking the archives, found may be similar kind of issues in the 2007-July archives. But how it has been solved if someone describes me that will be really helpful. In our case, just at the problem started found

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

System info: # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686-bigmem i686 Debian squeeze/sid .. mail_plugins: readonly .. I have a requirement to have read-only to a mailbox. I have been researching through the wiki, the mailing list archives and good old Google. There was a number of similar questions with no real definitive answer. Option 1: ACL This can work, but not if the

Hello, Today a virtual server under my administration ran out of disk space, so I had to get extra space to it.. while it was running, because it's an important web server without any kind of HA/Load Balancing (don't do that, kids). So what happened, is that after another administrator had extended the disk from VMWare, I tried to extend it from the OS side. Everything went well,

Hi, I'm trying to set up samba share exporting gpfs filesystem and I strugle with setting sharemode to yes. Samba is 3.6.5, gpfs version is 3.2.1-29 (the latest available for 3.2 branch). Everything works fine when sharemode is set to no, but I'd rather insist to switch it to yes. That's what man page says: no - do not propagate sharemodes across all GPFS nodes. This should only be