Thanks for the responses.
I’m sorry if this is a bit long winded but I thought that explaining the
context might assist in describing the proposed solution.
I work for a University and we have an artificially high number of user
accounts. We have applicants, current students and those that
On 6/16/2010 6:55 AM, Scott Kaelin wrote:
On Wed, Jun 16, 2010 at 6:03 AM, Orvar Korvar
knatte_fnatte_tja...@yahoo.com
mailto:knatte_fnatte_tja...@yahoo.com wrote:
You can't expand a normal RAID, either, anywhere I've ever seen.
Is this true?
Depending on the software/hardware you
On 17/06/2010 09:18, MichaelHoy wrote:
First thing, it’s simply not practical to have so many file systems. I’d
already tested 5k and boot time was unacceptable, never mind the other inherent
implications of such a strategy. Therefore, access to Previous Versions via
Windows is out.
Could you import it back on the original server with
Zpool import -f newpool rpool?
Jay
-Original Message-
From: Brandon High [mailto:bh...@freaks.com]
Sent: Wednesday, June 16, 2010 2:19 PM
To: Seaman, John
Cc: zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] mount zfs boot disk
Guys,
# zpool iostat pool1
capacity operationsbandwidth
pool used avail read write read write
-- - - - - - -
pool1822M 927G 0 0435 28.2K
In which units is bandwidth measured?
I suppose capital K
OCZ not only introduced these enterprise SSDs but also Maximum
Performance/Enterprise Solid State Drives a couple of days ago.
An SLC version: Vertex 2 EX
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of MichaelHoy
First thing, it’s simply not practical to have so many file systems.
I’d already tested 5k and boot time was unacceptable, never mind the
other inherent implications of such a
When somebody is hammering on the system, I want to be able to detect who's
doing it, and hopefully even what they're doing.
I can't seem to find any way to do that. Any suggestions?
Everything I can find ... iostat, nfsstat, etc ... AFAIK, just show me
performance statistics and so
I upgraded a server today that has been running SXCE b111 to the
OpenSolaris preview b134. It has three pools and two are fine, but one
comes up with no space available in the pool (SCSI jbod of 300GB disks).
The zpool version is at 14.
I tried exporting the pool and re-importing and I get
From: Fredrich Maney [mailto:fredrichma...@gmail.com]
Have you looked at 'lsof' or the native BSM auditing features?
Admittedly audit is not really intended for realtime, but lsof
certainly is.
I'm not familiar with the BSM auditing, and audit, that you mentioned. Any
pointers?
lsof and
You can turn on NFS auditing with the sharenfs option rw=host1:host2,log.
Audit logs are in /var/nfs. I believe there's a bit of setup in
/etc/nfs/nfslog.conf and /etc/default/nfslogd, but I think I'm running fine off
of defaults. This only works for NFSv3. NFSv4 won't log.
--
Cameron
Oh, and start /usr/lib/nfs/nfslogd. If you just set sharenfs, nfslogd won't
start automatically, but it will at reboot.
-
Cameron Hanover
chano...@umich.edu
Our integrity sells for so little, but it is all we really have. It is the
very last inch of us, but within that inch, we are free.
On 17/06/2010 14:12, Edward Ned Harvey wrote:
From: Fredrich Maney [mailto:fredrichma...@gmail.com]
Have you looked at 'lsof' or the native BSM auditing features?
Admittedly audit is not really intended for realtime, but lsof
certainly is.
I'm not familiar with the BSM auditing, and audit,
answer for your questions:
usr/src/cmd/zpool/zpool_main.c
} else {
print_one_stat(newvs-vs_alloc);
print_one_stat(newvs-vs_space - newvs-vs_alloc);
}
print_one_stat((uint64_t)(scale * (newvs-vs_ops[ZIO_TYPE_READ] -
Kinda old topic, but I ran into the same error, I found a (dirty) workaround
for it.
First, the reason for this is that you are booting a u8 image to restore a u7
or flasharchive, right?
zpool jumped from version 10 to version 15 with u8. Jumpstart profiles create a
rpool version 15, there
Kinda old topic, but I ran into the same error, I found a (dirty) workaround
for it.
First, the reason for this is that you are booting a u8 image to restore a u7
or flasharchive, right?
zpool jumped from version 10 to version 15 with u8. Jumpstart profiles create a
rpool version 15, there
Don't know why my posts are not displayed properly...
Here is the workaround in a txt file: http://bzflag.free.fr/zfs.txt
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Hi--
ZFS command operations involving disk space take input and display using
numeric values specified as exact values, or in a human-readable form
with a suffix of B, K, M, G, T, P, E, Z for bytes, kilobytes, megabytes,
gigabytes, terabytes, petabytes, exabytes, or zettabytes.
Thanks,
Cindy
The EX specs page does list the supercap
The pro specs page does not.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Hi--
ZFS command operations involving disk space take input and display using
numeric values specified as exact values, or in a human-readable form
with a suffix of B, K, M, G, T, P, E, Z for bytes, kilobytes, megabytes,
gigabytes, terabytes, petabytes, exabytes, or zettabytes.
Let's play
I just lookup it up again and as far as i can see the super cap is present in
the MLC version as well as the SLC
http://www.ocztechnology.com/products/solid-state-drives/2-5--sata-ii/maximum-performance-enterprise-solid-state-drives/ocz-vertex-2-pro-series-sata-ii-2-5--ssd-.html
From the page:
On Thu, Jun 17, 2010 at 09:42:44AM -0700, F. Wessels wrote:
I just lookup it up again and as far as i can see the super cap is
present in the MLC version as well as the SLC
Very nice. A pair of the 50GB SLC model would be great for ZIL. Might
continue to stick with the X-25M for L2ARC though
On 17 jun 2010, at 18.17, Richard Jahnel wrote:
The EX specs page does list the supercap
The pro specs page does not.
They do for both on the Specifications tab on the web page:
On Thu, June 17, 2010 09:36, Darren J Moffat wrote:
On 17/06/2010 14:12, Edward Ned Harvey wrote:
From: Fredrich Maney [mailto:fredrichma...@gmail.com]
Have you looked at 'lsof' or the native BSM auditing features?
Admittedly audit is not really intended for realtime, but lsof
certainly is.
I'm not sure about the right naming, but here is what I did and what my
problem is now:
I imported a syspool as another name (that's why I use the naming
alias), using the following command: zpool import -f syspool original
My problem is that after reboot, the syspool is available both as
syspool
On 6/17/2010 10:06 AM, Jerome Warnier wrote:
I'm not sure about the right naming, but here is what I did and what my
problem is now:
I imported a syspool as another name (that's why I use the naming
alias), using the following command: zpool import -f syspool original
My problem is that after
Also, the disks were replaced one at a time last year from 73GB to 300GB to
increase the size of the pool. Any idea why the pool is showing up as the
wrong size in b134 and have anything else to try? I don't want to upgrade
the pool version yet and then not be able to revert back...
On Thu, Jun 17, 2010 at 9:58 AM, Ray Van Dolson rvandol...@esri.com wrote:
Do the drives keep any sort of internal counter so you get an idea of
how much of the rated drive lifetime you've chewed through?
I think that it's reported via SMART.
-B
--
Brandon High : bh...@freaks.com
Hi Ben,
Any other details about this pool, like how it might be different from
the other two pools on this system, might be helpful...
I'm going to try to reproduce this problem.
We'll be in touch.
Thanks,
Cindy
On 06/17/10 07:02, Ben Miller wrote:
I upgraded a server today that has been
Ye
man nfslogd
(and google nfslogd, etc)
totally nailed it. Thank you Cameron.
Just incase anyone stumbles across this by search, here's the start-to-end
answer:
man nfslogd
First, edit /etc/default/nfslogd I am using:
MIN_PROCESSING_SIZE=1
IDLE_TIME=1
Assuming you
So I've been working on solving a problem we noticed that when using
certain hot pluggable busses (think SAS/SATA hotplug here), that
removing a drive did not trigger any resulting response from either FMA
or ZFS *until* something tried to use that device. (This removal of a
drive can be thought
Cindy,
The other two pools are 2 disk mirrors (rpool and another).
Ben
Cindy Swearingen wrote:
Hi Ben,
Any other details about this pool, like how it might be different from
the other two pools on this system, might be helpful...
I'm going to try to reproduce this problem.
We'll
On Jun 17, 2010, at 3:52 PM, Garrett D'Amore wrote:
Anyway, I'm happy to share the code, and even go through the
request-sponsor process to push this upstream. I would like the
opinions of the ZFS and FMA teams though... is the approach I'm using
sane, or have I missed some important
On Thu, 2010-06-17 at 16:16 -0400, Eric Schrock wrote:
On Jun 17, 2010, at 3:52 PM, Garrett D'Amore wrote:
Anyway, I'm happy to share the code, and even go through the
request-sponsor process to push this upstream. I would like the
opinions of the ZFS and FMA teams though... is the
On Jun 17, 2010, at 4:35 PM, Garrett D'Amore wrote:
I actually started with DKIOCGSTATE as my first approach, modifying
sd.c. But I had problems because what I found is that nothing was
issuing this ioctl properly except for removable/hotpluggable media (and
the SAS/SATA
On Thu, 2010-06-17 at 17:53 -0400, Eric Schrock wrote:
On Jun 17, 2010, at 4:35 PM, Garrett D'Amore wrote:
I actually started with DKIOCGSTATE as my first approach, modifying
sd.c. But I had problems because what I found is that nothing was
issuing this ioctl properly except for
On Jun 17, 2010, at 12:48 PM, Edward Ned Harvey wrote:
Ye
man nfslogd
(and google nfslogd, etc)
totally nailed it. Thank you Cameron.
Before you get too happy... NFS logging can have a severe negative
impact on performance and scaling. Not recommended for anyone
with lots of
On Jun 17, 2010, at 6:13 PM, Garrett D'Amore wrote:
So how do you diagnose the situation where someone trips over a cable,
or where the drive was bumped and detached from the cable? I guess I'm
OK with the idea that these are in a REMOVED state, but I'd like the
messaging to say something
Hi,
I replaced one faulty disk with a new disk in the same disk slot. The faulty
disk has a device name as c2t6d0. I expect the system would use the same device
name for the new disk. However, it did not. Instead, the system uses c2t14d0,
which is next free available device name, for the new
On 18/06/10 09:00 AM, Simon Gao wrote:
Hi,
I replaced one faulty disk with a new disk in the same disk slot. The
faulty disk has a device name as c2t6d0. I expect the system would use
the same device name for the new disk. However, it did not. Instead,
the system uses c2t14d0, which is next
On Thu, 2010-06-17 at 18:38 -0400, Eric Schrock wrote:
On Jun 17, 2010, at 6:13 PM, Garrett D'Amore wrote:
So how do you diagnose the situation where someone trips over a cable,
or where the drive was bumped and detached from the cable? I guess I'm
OK with the idea that these are in a
Thanks James.
Yes. The controller is LSI Logic SAS1068E.
When device name changed, the following command as described by ZFS
documentation will fail:
zpool replace mypool old_disk_name
Instead one must use:
zpool replace mypool old_disk_name new_disk_name
ZFS document says if replacing
Hi,
I replaced one faulty disk with a new disk in the
same disk slot. The faulty disk has a device name as
c2t6d0. I expect the system would use the same device
name for the new disk. However, it did not. Instead,
the system uses c2t14d0, which is next free available
device name, for the
Hi guys
I wanted to ask how i could setup a iSCSI device to be shared by 2 computers
concurrently, by that i mean sharing files like it was a NFS share but use
iSCSI instead.
I tried and setup iSCSI on both computers and was able to see my files (I had
formatted it NTFS before), from my
44 matches
Mail list logo
