search for: tizzy

Ok for those of you all up in a tizzy over my subject line, please don't take it literally because I'm certainly not saying that asterisk is the problem here. I just got a little nightmare problem that I need a bit of help figuring out. I installed an asterisk system a few months ago for a client, it has run almost flawlessly...

...turn code = 0x06000000 end_request: I/O error, dev sdd, sector 29792313 Both (all) iSCSI devices are failed. Under iostat I see activity to the iSCSI block devices, and the whole machine acts mostly I/O blocked (even the Fedora 10 DomU running on flat files will start throwing nagios into a tizzy). If I do 'service iscsi stop' everything picks right back up (though the DomU using them as its disks is obviously unhappy). When I start iscsi again I can pick right back up (after repairing filesystems in the DomU), and I can repeat the process at will. Sometimes the disks will come...

I think I understand what Active Directory is all about. I understand LDAP and I understand Kerberos. I can see how AD (well, Kerberos actually) enables single-sign-on (I assume it deals in tickets with the Windows clients as standard Kerberos clients do) and can make life easy in a large network (which, IIRC was one of the design goals of Kerberos in the first place). But lets say I have a

I''ve got a form with inputs like user[first_name], user[last_name], etc. When editing the user instead of creating a new one I include a user[id]. I then try and save the object using: user = User.new(params[:user]) user.save() I would *expect* that since I included the user[id] it should do an update and should call validate_on_update. But this doesn''t appear to be the

All, As much as I hate to ask, how is this project coming along? We are approaching the 4 month post-release point... -David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110404/1e9862bd/attachment-0005.html>

Here is a proposal for a new ''copies'' property which would allow different levels of replication for different filesystems. Your comments are appreciated! --matt A. INTRODUCTION ZFS stores multiple copies of all metadata. This is accomplished by storing up to three DVAs (Disk Virtual Addresses) in each block pointer. This feature is known as "Ditto Blocks". When

Here is a proposal for a new ''copies'' property which would allow different levels of replication for different filesystems. Your comments are appreciated! --matt A. INTRODUCTION ZFS stores multiple copies of all metadata. This is accomplished by storing up to three DVAs (Disk Virtual Addresses) in each block pointer. This feature is known as "Ditto Blocks". When