Wrong Shutdown
Hello guys, I have a machine with a HardDrive with a slice of 2.7TB, and I have no UPS.. when sometimes I have power failure, and consequently a wrong shutdown, The fsck spends much time to recover the filse system, what can I do? I need to be faster. Thanks in advance. -- Walter Neto Analista Desenvolvedor
Re: Wrong Shutdown
Why OpenBSD has no interest in using journal file system? On Mon, May 26, 2014 at 10:48 AM, Theo de Raadt dera...@cvs.openbsd.orgwrote: I have a machine with a HardDrive with a slice of 2.7TB, and I have no UPS.. when sometimes I have power failure, and consequently a wrong shutdown, The fsck spends much time to recover the filse system, what can I do? I need to be faster. Get a UPS. fsck is required to ensure the directory hierarchy is coherent. -- Walter Neto Analista Desenvolvedor
Re: Wrong Shutdown
So do you have interest? I have interest in help.. I love OpenBSD project and I want to use it in everything. And let's work in World Peace too.. :) On Mon, May 26, 2014 at 10:58 AM, Theo de Raadt dera...@cvs.openbsd.orgwrote: Why OpenBSD has no interest in using journal file system? Because we simply don't have anyone working on it at the moment. What is so hard to understand about that? We are a group of volunteers! We work on what we want to, and as a group we don't try to overcommit our efforts into specific directions at the impact towards other directions. As far as I know, none of the developers are specifically working on World Peace, either. -- Walter Neto Analista Desenvolvedor
Re: Wrong Shutdown
On Mon, May 26, 2014 at 11:09 AM, Theo de Raadt dera...@cvs.openbsd.orgwrote: So do you have interest? I have interest in help.. I love OpenBSD project and I want to use it in everything. There is a large gap between how do I make fsck faster without buying a UPS and I will help give you guys a working journal filesystem. I don't know you, maybe I am misinterpreting you. I made the question first because I have learned many different best ways than usual using OBSD, and I think that was better to question first. And let's work in World Peace too.. :) Your makeup has a smudge, so you don't win. -- Walter Neto Analista Desenvolvedor
IBM System x3100 M4 - panic
Hello guys, I am trying to install the OpenBSD 5.1 on x3100 M4 and I got a panic after installation while booting, unfortunately it has only USB and no serial port and I can't type trace to get information. Here is what I got on my screen: acpicpu3 at acpi0: PSS acpibtn0 at acpi0: PWRB ipmi at mainbus0 not configured cpu0: Enhanced SpeedStep 3093 MHz: speeds: 3100, 3000, 2900, 2800, 2700, 2600, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600 MHz pci0 at mainbus0 bus 0 extent_alloc_region: extent 'pcimem' (0x0 = 0xf) extent_alloc_region: start 0x3088c1b0, end 0x3088c1b000ff panic: extent_alloc_region: region lies outside extent Stopped at Debugger+0x5: leave Debugger() at Debugger+0x5 panic() at panic+0xe4 extent_alloc_region() at extent_alloc_region+0xb5 pci_reserve_resources() at pci_reserve_resources+0x116 pci_probe_device() at pci_probe_device+0x21b pci_enumerate_bus() at pci_enumerate_bus+0xe9 pciattach() at pciattach+0x107 config_attach() at config_attach+0x1d4 mainbus_attach() at mainbus_attach+0x165 config_attach() at config_attach+0x1d4 end trace frame: 0x80e6ae90, count: 0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO. DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb{0} Thanks in advance, Walter Neto - Ribeirão Preto - SP, Brazil
Re: IBM System x3100 M4 - panic
Sorry guys, I try to install the 5.2-current too, the same output. thanks. 2012/10/12 Walter Souza wsouz...@gmail.com: Hello guys, I am trying to install the OpenBSD 5.1 on x3100 M4 and I got a panic after installation while booting, unfortunately it has only USB and no serial port and I can't type trace to get information. Here is what I got on my screen: acpicpu3 at acpi0: PSS acpibtn0 at acpi0: PWRB ipmi at mainbus0 not configured cpu0: Enhanced SpeedStep 3093 MHz: speeds: 3100, 3000, 2900, 2800, 2700, 2600, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600 MHz pci0 at mainbus0 bus 0 extent_alloc_region: extent 'pcimem' (0x0 = 0xf) extent_alloc_region: start 0x3088c1b0, end 0x3088c1b000ff panic: extent_alloc_region: region lies outside extent Stopped at Debugger+0x5: leave Debugger() at Debugger+0x5 panic() at panic+0xe4 extent_alloc_region() at extent_alloc_region+0xb5 pci_reserve_resources() at pci_reserve_resources+0x116 pci_probe_device() at pci_probe_device+0x21b pci_enumerate_bus() at pci_enumerate_bus+0xe9 pciattach() at pciattach+0x107 config_attach() at config_attach+0x1d4 mainbus_attach() at mainbus_attach+0x165 config_attach() at config_attach+0x1d4 end trace frame: 0x80e6ae90, count: 0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO. DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb{0} Thanks in advance, Walter Neto - Ribeirão Preto - SP, Brazil