search for: 134g

<copied from opensolaris-dicuss as this probably belongs here.> I kept on trying to migrate my pool with children (see previous threads) and had the (bad) idea to try the -d option on the receive part. The system reboots immediately. Here is the log in /var/adm/messages Feb 8 16:07:09 amber unix: [ID 836849 kern.notice] Feb 8 16:07:09 amber ^Mpanic[cpu1]/thread=ffffff014ba86e40: Feb 8

...f storage at 6 PM. and when i checked messages log file,I saw faillog under /var/log directory like below: -rw------- 1 root root 137438953440 Oct 24 15:39 faillog its ~136 GB but my disk table size like below: /dev/md1 497G 19G 453G 4% / /dev/md3 157G 15G 134G 10% /backup /dev/md0 243M 21M 210M 9% /boot tmpfs 32G 0 32G 0% /dev/shm /dev/sdc 805G 25G 739G 4% /mnt/sdc Where is ~136 GB faillog file ? I tried force fsck but no error i have. but i worried,Something is wrong ? I have a error about...

Hello: I have set up a DAV file system on my apache server using these directives in ssl.conf: Alias /files /var/www/files <Directory /var/www/files> Dav On AuthType Basic AuthName "Filesystem access" AuthUserFile /var/www/files.passwd require valid-user Options Indexes </Directory> On my client machine (Windows XP SP3), I am able to add the https location

Just look at this. I thought all the restarting resilver bugs were fixed, but it looks like something odd is still happening at the start: Status immediately after starting resilver: # zpool status pool: rc-pool state: DEGRADED status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine

Hi All, I am running on CentOS Released 6.1 final. Been using and running Linux KVM quite well for quite some time, something goes wrong after I perform yum upgrade. I created new VM yesterday without any problem, same exact installation procedure, installed FreeBSD 8.2. I tried to create a new VM today after yum upgrade, it's able to detect the hard disk, when I start commit FreeBSD 8.2