similar to: zfs failsafe pool mismatch

I have some clients that run centos6 and I need to have users be able to access the "failsafe terminal" from the login screen. The old options (from 4/5) for choosing your session aren't present. I've googled a bit on this but don't seem to be using a good search string as most of the hits have nothing to do with this and the rest aren't helpful. So, just wondering

Used to, when I had an error in development mode, I saw a pretty stack trace in the browser and didn''t have to go the server console, and in production mode I would see the pretty 500.html error page be displayed. Since I''ve started using Rails 2.2, I no longer get either of these. I get the ugly black and white "500 Internal Server Error" message. The happens the

I am trying to find out why form_tag with remote => true is not sending an ajax response and only sending HTML. I have started a basic Rails App with two pages and am following the Railscast 205 UJS example. Every time I include:- <%= form_tag homepages_path, :method => ''get'', remote => true do %> I get from the server(WEBrick):- (Ruby 1.9.2 and Rails 3) A 500

Hello folks, I have a question and a small problem... I did try to replicate my zfs with all the snaps, so I did run few commands: time zfs send mypool/d at 2006_month_10 | zfs receive mypool2/d at 2006_month_10 real 6h35m12.34s user 0m0.00s sys 29m32.28s zfs send -i mypool/d at 2006_month_10 mypool/d at 2006_month_12 | zfs receive mypool/d at 2006_month_12 real 4h49m27.54s user

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

There are times when ZFS options can not be applied at the moment, i.e. changing desired mountpoints of active filesystems (or setting a mountpoint over a filesystem location that is currently not empty). Such attempts now bail out with messages like: cannot unmount ''/var/adm'': Device busy cannot mount ''/export'': directory is not empty and such. Is it

For the mailing list archive and for anyone else interested. A few years ago we needed to automatically run a second AGI if the first AGI failed i.e. a "failsafe" setup. Mainly because I'm not a very good programmer. 8-| The code below is very similar to what we use in production. This code is also at http://pastebin.com/LBaLhdfJ for a while. "sm" stands for Switch

Hi everyone I am currently testing Solaris 11 Express. I currently have a root pool on a mirrored pair of small disks, and a data pool consisting of 2 mirrored pairs of 1.5TB drives. I have enabled auto snapshots on my root pool, and plan to archive the daily snapshots onto my data pool. I was wondering how easy it would be, in the case of a root pool failure (i.e. both disks giving up the

Hi, once I created a zpool of single vdevs not using mirroring of any kind. Now I wonder if it''s possible to add vdevs and mirror the currently existing ones. Thanks, budy -- This message posted from opensolaris.org

> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- > bounces at opensolaris.org] On Behalf Of bob netherton > > You can, with recv, override any property in the sending stream that can > be > set from the command line (ie, a writable). > > # zfs send repo/support at cpu-0412 | zfs recv -o version=4 repo/test > cannot receive: cannot override received

I'm admin on a samba PDC with 150 users, and as normal users they are quit "stupid". This means that they ofte deletes something that shouldnt have been deleted. And I find it anoying to restore their files from tapebackup. So would it be possible to get samba to "move" files instead of deleting them? This way I could allocate a disk to store deleted files for a periode of

Hello all. I am new...very new to opensolaris and I am having an issue and have no idea what is going wrong. So I have 5 drives in my machine. all 500gb. I installed open solaris on the first drive and rebooted. . Now what I want to do is ad a second drive so they are mirrored. How does one do this!!! I am getting no where and need some help. -- This message posted from opensolaris.org

Hi, I''m creating the file upload code in a C# web form to upload to my Rails app. When I start the upload I get the following error on my Rails server? Any ideas how I can fault find here? It could be the case the HTTP post I''m creating has a problem (it'' multipart, with a file upload + some form parameters) however it''s hard to tell from Rails what it is

I am trying to give a general user permissions to create zfs filesystems in the rpool. zpool set=delegation=on rpool zfs allow <user> create rpool both run without any issues. zfs allow rpool reports the user does have create permissions. zfs create rpool/test cannot create rpool/test : permission denied. Can you not allow to the rpool? -- This message posted from opensolaris.org

The time has come to review the current Contributor and Core contributor grants for ZFS. Since all of the ZFS core contributors grants are set to expire on 02-24-2009 we need to renew the members that are still contributing at core contributor levels. We should also add some new members to both Contributor and Core contributor levels. First the current list of Core contributors: Bill

Hi, We are using multiple opensolaris 06/09 and solaris 10 servers. Currently we are ''dumping'' (incremental)backups to a backup server. I wonder if anybody knows what happens when I send/recv a zfs volume from version 15 to a (backup) system with version 14. I''ve the feeling it''s not very wise to do, but is it doable and what kind of caveats can be

On some machines running PowerPath, there''s sometimes issues after an update/upgrade of the PowerPath software. Sometimes the pseudo devices get remapped and change names. ZFS appears to handle it OK, however sometimes it then references half native device names and half the emcpower pseudo device names. So the SA can easily be confused. Is there a way to tell ZFS which device names