Re: [OpenIndiana-discuss] linux disk filter

2013-04-18 Thread Michael Schuster
Hi, erm. This list is dedicated to OpenIndiana, which is NOT a flavour of linux. While userland may look similar in many aspects, the kernel most definitely does not, so even if you may get lucky and "find" someone who can help you, I'd suggest you look for a linux-oriented mailing list and ask th

[OpenIndiana-discuss] linux disk filter

2013-04-18 Thread DengEncore
Hi all, I am writing a linux kernel module to filter the disk IO. And I am facing the problems below: 1. When the system start, how can I set my module be loaded before the file system? If the file system is loaded first, maybe some disk IO will be out of filter before my module loaded.

Re: [OpenIndiana-discuss] building a new box soon- HDD concerns and recommendations for virtual serving

2013-04-18 Thread Carl Brewer
On 18/04/2013 11:08 AM, Jay Heyl wrote: One thing I would recommend is trying to use the ashift=12 setting to force the use of 4k blocks. I ran into problems because my initial pools were created with 512-byte blocks. When I bought some spare drives I couldn't use them because they were advanced

Re: [OpenIndiana-discuss] vdev reliability was: Recommendations for fast storage

2013-04-18 Thread Edward Ned Harvey (openindiana)
> From: Timothy Coalson [mailto:tsc...@mst.edu] > > As for what I said about resilver speed, I had not accounted for the fact > that data reads on a raid-z2 component device would be significantly > shorter than for the same data on 2-way mirrors. Depending on whether > you > are using enormous b

Re: [OpenIndiana-discuss] vdev reliability was: Recommendations for fast storage

2013-04-18 Thread Timothy Coalson
On Thu, Apr 18, 2013 at 10:24 AM, Sebastian Gabler wrote: > Am 18.04.2013 16:28, schrieb > openindiana-discuss-request@**openindiana.org > : > >> Message: 1 >> Date: Thu, 18 Apr 2013 12:17:47 + >> From: "Edward Ned Harvey >> (openindiana)" >> > >> >> To: Discussion list for OpenIndiana >>

Re: [OpenIndiana-discuss] IPNAT redirection.

2013-04-18 Thread dormitionsk...@hotmail.com
BTW - My solution was to make etherstubs, and create a virtual router, with my "working" zones in another network segment. Then everything works fine. See: http://www.c0t0d0s0.org/archives/5355-Upcoming-Solaris-Features-Crossbow-Part-1-Virtualisation.html It's actually simple to do. If I can

Re: [OpenIndiana-discuss] IPNAT redirection.

2013-04-18 Thread dormitionsk...@hotmail.com
On Apr 18, 2013, at 2:15 PM, Jonathan Adams wrote: > In the past I have used "delegate" to do port forwarding on our internal > servers, forwarding from a server directly connected to the internet, to > one that has no direct connection. > > I was about to set up delegate to do the same job, whe

[OpenIndiana-discuss] IPNAT redirection.

2013-04-18 Thread Jonathan Adams
In the past I have used "delegate" to do port forwarding on our internal servers, forwarding from a server directly connected to the internet, to one that has no direct connection. I was about to set up delegate to do the same job, when it struck me that I should be able to use ipfilter, via ipnat

Re: [OpenIndiana-discuss] vdev reliability was: Recommendations for fast storage

2013-04-18 Thread Sebastian Gabler
Am 18.04.2013 16:28, schrieb openindiana-discuss-requ...@openindiana.org: Message: 1 Date: Thu, 18 Apr 2013 12:17:47 + From: "Edward Ned Harvey (openindiana)" To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Recommendations for fast storage Message-ID:

Re: [OpenIndiana-discuss] Booting OpenIndiana from USB stick and different ports and different machines (One stick for all)

2013-04-18 Thread Jim Klimov
On 2013-04-18 16:31, Guenther Alka wrote: I have installed OpenIndiana server and OmniOS on 16 GB USB sticks. This works very well especially with modern fast sticks, ZFS boot mirror and atime set to off. The problem is, that I can only boot from the USB port that was used during setup. On other

Re: [OpenIndiana-discuss] vdev reliability was: Recommendations for fast storage

2013-04-18 Thread Jim Klimov
On 2013-04-18 15:57, Edward Ned Harvey (openindiana) wrote: I think you're misplacing a decimal, confusing bits for bytes, and mixing up exponents. Cuz you're way off. With merely 70 unknown *bits* that is, less than 10 bytes, you'll need a 3-letter government agency devoting all its computat

[OpenIndiana-discuss] Booting OpenIndiana from USB stick and different ports and different machines (One stick for all)

2013-04-18 Thread Guenther Alka
I have installed OpenIndiana server and OmniOS on 16 GB USB sticks. This works very well especially with modern fast sticks, ZFS boot mirror and atime set to off. The problem is, that I can only boot from the USB port that was used during setup. On other ports or mainboards, it crashes after se

Re: [OpenIndiana-discuss] vdev reliability was: Recommendations for fast storage

2013-04-18 Thread Edward Ned Harvey (openindiana)
> From: Jim Klimov [mailto:jimkli...@cos.ru] > > Well, thanks to checksums we can know which variant of userdata > is correct, and thanks to parities we can verify which bytes are > wrong in a particular block. If there's relatively few such bytes, > it is theoretically possible to brute-force mat

Re: [OpenIndiana-discuss] vdev reliability was: Recommendations for fast storage

2013-04-18 Thread Jim Klimov
On 2013-04-18 12:46, Sebastian Gabler wrote: I do not think that zfs will have better resilience against rot of parity data than conventional RAID. At best, block level checksums can help raise an error, so you know at least that something went wrong. But recovery of the data will probably not be

Re: [OpenIndiana-discuss] vdev reliability was: Recommendations for fast storage

2013-04-18 Thread Edward Ned Harvey (openindiana)
> From: Sebastian Gabler [mailto:sequoiamo...@gmx.net] > > AFAIK, a bit error in Parity or stripe data can be specifically > dangerous when it is raised during resilvering, and there is only one > layer of redundancy left. You're saying "error in parity," but that's because you're thinking of ra

Re: [OpenIndiana-discuss] Recommendations for fast storage

2013-04-18 Thread Edward Ned Harvey (openindiana)
> From: Jay Heyl [mailto:j...@frelled.us] > > I now realize you're talking about 8 separate 2-disk > mirrors organized into a pool. "mirror x1 y1 mirror x2 y2 mirror x3 y3..." Yup. That's normal, and the only way. > I also realize that almost every discussion I've seen online concerning > mirr

Re: [OpenIndiana-discuss] Recommendations for fast storage

2013-04-18 Thread Edward Ned Harvey (openindiana)
> From: Timothy Coalson [mailto:tsc...@mst.edu] > > Did you also compare the probability of bit errors causing data loss > without a complete pool failure? 2-way mirrors, when one device > completely > dies, have no redundancy on that data, and the copy that remains must be > perfect or some data

Re: [OpenIndiana-discuss] Recommendations for fast storage

2013-04-18 Thread Edward Ned Harvey (openindiana)
> From: Jay Heyl [mailto:j...@frelled.us] > > Ah, that makes much more sense. Thanks for the clarification. Now that you > put it that way I have to wonder how I ever came under the impression it > was any other way. I've gotten lost in the numerous mis-communications of this thread, but just to

[OpenIndiana-discuss] vdev reliability was: Recommendations for fast storage

2013-04-18 Thread Sebastian Gabler
Am 18.04.2013 03:09, schrieb openindiana-discuss-requ...@openindiana.org: Message: 1 Date: Wed, 17 Apr 2013 13:21:08 -0600 From: Jan Owoc To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Recommendations for fast storage Message-ID: Content-Type: text/plain;