Search results

Sorry for the Necro Posting, but I wanted to chime in how ridiculous it is that NexentaStor is marketed as enterprise class storage on commodity hardware.. and then basically the only ZIL anyone seems to suggest using (with a high degree of faith) is a $2,500 dollar STEC drive. Which isn't...

The partners are getting me better deals (by 20% ish).. problem is it's just not enough. I even considered buying the RAM and hard drives outside of Dell since there's some massive markup on those and the pricing still just doesn't fall in where I need it to be. (We're still talking $1k...

I live and work really REALLY close to Dell WHQ. I have friends who are in sales and I've tried to get them to get Dell to pry their death grip off pricing for us. So far they managed to knock an additional $250 off web pricing, which I'm already beating out going through a channel partner...

I got one vendor to knock down the Dell I was trying to buy down another $700ish. It's still a full grand over the whitebox solution for nearly identical hardware and support (3yr/NBD parts). I always hear the folks that say their rep at Dell beats any whitebox pricing.. but I've yet to find...

But it is _YOUR_ problem, regardless of the vendor because Dell's going to pass the buck to VMWare, and VMWare is going to pass the buck to Dell (or LSI if it's a PERC card).. and so on. I've played this game many times before.

Ok you have me there about decoding error strings, but I guarantee you that your first call to HP or Dell or whomever isn't gonna get you anyone who even knows what you're talking about. I've endured Dell's "Support" before.. and I'd rather not have to endure it again.

Can you elaborate? I mean if everything is HCL qualified what's the issue? Hardware on the server isn't going to be tossed out every 2 years in favor of a new board+chip due to having to chase down HCL approved components. I live 3 miles from Dell WHQ, and work 1.5 miles from WHQ and I've...

Yeah it would be production, eventually. That's more or less what I thought re: HCL. But what's wrong with whiteboxing if the components are on the HCL? I find the hardware more flexible than say, Dell. Not to mention weird vendor lock-ins on RAID cards and hard disks that sometimes are...

I used the AVVI agent and ran into a shit ton of issues as well. A Veeam rep got ahold of me and gave me a free license because I was harping on the Symantec forums about how much more Veeam can do for less. (Dedupe/Granular restores etc) without extra licensing.

I'm generally a whitebox server sort of guy. I'm in a bit of a quandary I was wondering if anyone could help me decipher. I was putting together a box via Silicon Mechanics, they list it under their "Virtualization Servers", so naturally I assumed it was on the HCL. Turns out the board in...

True, but a ZFS backend on an iSCSI ZVOL isn't much good. It just keeps the blocks in-check on the ZFS side. It doesn't help with corruption or data issues within the ZVOL (unfortunately). So it's not a great solution.

You'll be wasting a perfectly good RAID card for ZFS. Sure you can set the disks in JBOD but you'd be better off (IMHO) with a 'simple' HBA.

Ok you're contradicting yourself. Above you say "optimal" config for 4K disks is: But then you're saying that vdev size is not factored by sector size. So which is it? Then you also go on to say that generally smaller vdev groups are ideal but then suggest up to 18 disks (16 disks + 2 parity)...

You didn't say RAIDZ1 or 2? From what the Wiki states, anything between 3 and 9 per vdev is acceptable.

I thought 512b drives had a similar "optimal" configuration not dissimilar of the 128 / N suggested here. The ZFS Tuning wiki doesn't seem to make the distinction on of which drive (sector wise) fit into the "optimal" config that I can see.

Have you tried massaging the screen? Sometimes stuck pixels get fixed with some light pressure. No joke. What else have you got to lose while you wait for a new display?

Nexenta is supposedly working for better analytics in 3.1 or 4.0 (not sure which yet).. I've been "running" it since the early 2.0 days, and by "running" it I mean fighting Kerberos/AD issues with their enterprise support dept ... 3.0.3 fixed a LOT of stuff in that regard, but to be fair all...

What's under your "NAT" configuration under Firewall? I find configging NAT configs the corresponding firewall rules appropriately. The firewall comments/remarks lead me to believe you didn't configure them via NAT since they usually say things like UDP PORT 53 NAT etc...

Man I so wish that Sun would have tossed Amber Road/Fishworks out for mass consumption before they got swallowed by Oracle. I so want a Sun/Oracle ZFS appliance, but not at the prices they want.

Where did the board come from?

I follow tech companies for news on new stuff. It's definitely got it's uses even if you think it's just for following beiber and lady gaga.

I want some ATX sized boards from SMC. Not these mini-ATX guys. Grumble.

go partition and format it as these other guys have mentioned.

that's "ditto"

tweetdeck is a steaming pile.

loan

Server 08 no longer requires additional metadata cleanup. It'll do it for you when you remove the DC via ADUC. Just FYI.

I've never heard of it prior to joining [H], so still call me skeptical. ;)

The 08 server crash wasn't necessarily a ESET problem. I've been following the issue on wilderssecurity.com I run v 3.x right now on my SBS 2008 since I haven't had time to upgrade and remove the MS filter driver causing the issue...

So you keep on saying. What's your stake in the company. :rolleyes:

But... But ... THINK OF THE FARMERS!!

If you clone a snapshot just make another target out of it and check the FS for consistency or pull the file you want. I'm not advocating blowing away the original target for a recovery. As far as shutting down the initiator, I'd either bring the other LUN up in the same initiator or use...

ATX 40 years? Not quite that long, just 15. The SR2 is that big due to dual processors, tons of RAM slots and so on. It's basically server board size.

iSCSI unmap that's been added to Illumos will fix this problem. :) Though, using Nexenta here at home and work with iSCSI LUNS. Yes eventually the iSCSI LUN would balloon up to it's provisioned size, however the capacity will change upon write/deletions within the mounted LUN. So, I'm not so...

This might be it... Thanks. http://www.panduit.com/groups/MPM-OP/documents/InstallationInstruction/103199.pdf Yep, that's 'em.

Or they take a day off? Or this happens to be their day off? Or a myriad of other reasons that don't make them "rich" or "bums" (whichever way you look at it)

The initiator is going to see whatever you provision the ZVOL as. if you make it 10TB it'll see it as 10TB.

Not having to work? How do you figure?

You can "thin provision" the ZVOL as big as you want it. Just watch that the ZVOL doesn't use more space than you actually have. As far as keeping up with ZVOL growth, expanding the array will help there. "growing" fixed size ZVOL's isn't really doable. That is, when I've changed the ZVOL...

You have to imagine? have you never used an ear bud?