Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
2.6.21-ragnarok1: "Dripping Venom"
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
yngwin
Retired Dev
Retired Dev


Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China

PostPosted: Sun Apr 29, 2007 12:14 am    Post subject: 2.6.21-ragnarok1: "Dripping Venom" Reply with quote

I'm sharing this patchset here, though major kudos go to vipernicus, predatorfreak, Waninkoko, as well as the devs from Gentoo Linux and Arch Linux, who are all sources and maintainers of various patches that I have included here. I've also added a few extra things from -mm, as well as the -git2 update from Linus.

The major reason I made this patchset is that I wanted the stable Reiser4 patch from 2.6.20-viper4, combined with SD and some other updates, in a fresh 2.6.21(.1) kernel. Please test and let let me know how things work.

Included patches are:
Quote:
patch-2.6.21-git2
ragnarok-version.patch
2.6.21-sd-0.46.patch
2.6.21-sd-0.46-boost.patch
2.6.21-sd-0.46-boost-tunable.patch
genpatches-rollup-2.6.21-1.patch
ck-desktop-rollup-2.6.21.patch
cpu-support-rollup.patch
rcu-preempt-rollup-2.6.21.patch
adaptive-readahead-2.6.21.patch
realtime-lsm.patch
linux-phc-0.2.9-for-2.6.21.patch
fs-ext4-2.6.21-update1.patch
reiser4-2.6.20.patch
driver-coretemp-2.6.21.patch
daconfig-2.3.1-2.6.21.patch
is_power_of_2-in-fat.patch
is_power_of_2-in-fs-block_devc.patch
unionfs-2.6.21-u2.diff
suspend2-2.2.9.13-for-2.6.21.patch
thinkpad-for-2.6.21-1.patch
sony-laptop-rollup-2.6.21.patch
acpi-dsdt-initrd-v0.8.4-2.6.21.patch
alsa.patch
alsa-include.patch
atkbd.patch
mactel-linux-2.6.21.patch
toshiba-bluetooth.patch
toshiba-acpi.patch
usb-storage-unusual-devs.patch


You can use the ebuild for ragnarok-sources in the berkano overlay, or apply the patch yourself, which can be downloaded from:
http://berkano.net/files/gentoo/ragnarok-sources/2.6.21/patch-2.6.21-ragnarok1.bz2
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sun Apr 29, 2007 8:23 am    Post subject: Reply with quote

you obviously don't have an exec-shield patch included, I'm going to test the plain patchset & see if the problems were caused by exec-shield (which is included in several patch-sets) :roll:

*fingers crossed*

update:

ok, I do not know if those problems were caused by exec-shield, but I'm running your kernel right now on a reiser4 partition with cryptcompress + lzo1 & it seems to be rocksolid, no corruptions during kernel-compile & nvidia-drivers emerge until now so far ...
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa

Hardcore Gentoo Linux user since 2004 :D
Back to top
View user's profile Send private message
darklegion
Guru
Guru


Joined: 14 Nov 2004
Posts: 468

PostPosted: Sun Apr 29, 2007 11:43 am    Post subject: Reply with quote

kernelOfTruth wrote:
you obviously don't have an exec-shield patch included, I'm going to test the plain patchset & see if the problems were caused by exec-shield (which is included in several patch-sets) :roll:

*fingers crossed*

update:

ok, I do not know if those problems were caused by exec-shield, but I'm running your kernel right now on a reiser4 partition with cryptcompress + lzo1 & it seems to be rocksolid, no corruptions during kernel-compile & nvidia-drivers emerge until now so far ...


Its not noexec causing it.I run with noexec=off in my kernel commandline (because mupen64 doesn't work correctly with it on) and have had the reiser4 bug on viper7 and viper10.
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sun Apr 29, 2007 12:04 pm    Post subject: Reply with quote

ok, thanks for clearing that,

so it must be some other variable, at least it's working now, so perhaps something's wrong with the default 'plugin', cryptcompress seems to work fine, let's see if it still works after some days of heavy compiling & everyday work
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa

Hardcore Gentoo Linux user since 2004 :D
Back to top
View user's profile Send private message
yngwin
Retired Dev
Retired Dev


Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China

PostPosted: Sun Apr 29, 2007 12:40 pm    Post subject: Reply with quote

darklegion wrote:
have had the reiser4 bug on viper7 and viper10.

I've definitely had it in viper7 as well. But I ran viper4 for a long time without problems, and other people have mentioned that too. That's why I went for the reiser4 patch that was included in viper4. It seems to be a good choice as I haven't run into the 0-byte bug with this.
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
Pse
Apprentice
Apprentice


Joined: 01 Mar 2005
Posts: 188
Location: by the plate river

PostPosted: Sun Apr 29, 2007 1:31 pm    Post subject: Reply with quote

kernelOfTruth, what R4 patch are you using? Are you using reiser4progs-1.0.6 from portage too? I'd like to give cryptcompress a ride.
Quote:
I've definitely had it in viper7 as well. But I ran viper4 for a long time without problems, and other people have mentioned that too. That's why I went for the reiser4 patch that was included in viper4. It seems to be a good choice as I haven't run into the 0-byte bug with this.

I think kernelOfTruth ran into the problem with viper4. I haven't, though. R4 from viper4 seems stable.
Back to top
View user's profile Send private message
_sys/sid
Guru
Guru


Joined: 27 Aug 2004
Posts: 346
Location: Asola (Mantova)

PostPosted: Sun Apr 29, 2007 1:33 pm    Post subject: Reply with quote

Here works without problem
Code:

Linux hashley 2.6.21-ragnarok1 #1 SMP PREEMPT Sun Apr 29 15:13:02 CEST 2007 i686 Intel(R) Pentium(R) 4 CPU 2.60GHz GenuineIntel GNU/Linux

Thanks
_________________
http://th30z.netsons.org/
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sun Apr 29, 2007 2:38 pm    Post subject: Reply with quote

Pse wrote:
kernelOfTruth, what R4 patch are you using? Are you using reiser4progs-1.0.6 from portage too? I'd like to give cryptcompress a ride.
Quote:
I've definitely had it in viper7 as well. But I ran viper4 for a long time without problems, and other people have mentioned that too. That's why I went for the reiser4 patch that was included in viper4. It seems to be a good choice as I haven't run into the 0-byte bug with this.

I think kernelOfTruth ran into the problem with viper4. I haven't, though. R4 from viper4 seems stable.


yes, you're right I did ran into those mentioned problems, don't know why it now works without problems, the only change is:

using ragnarok1, without exec-shield (instead of viper- 2.6.21-releases with replaced 2.6.20-viper4 replaced reiser4 patch), cryptcompress lzo1 partition (/root partition) instead of normal mkfs.reiser4 command

Quote:
dep -e reiser4progs
sys-fs/reiser4progs:
[ ] 1.0.5 (0)
[ I] 1.0.6 (0)


those reiser4progs are from portage, indeed, format commands were:

Code:
mkfs.reiser4 -o create=ccreg40,compress=gzip1 /dev/foo
mkfs.reiser4 -o create=ccreg40,compress=lzo1 /dev/foo

I've created them from within small-gentoo x86 r9

good luck with reiser4 & this kernel, all to you :)
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa

Hardcore Gentoo Linux user since 2004 :D
Back to top
View user's profile Send private message
_pF_
Apprentice
Apprentice


Joined: 22 Apr 2004
Posts: 195
Location: Central London

PostPosted: Sun Apr 29, 2007 7:36 pm    Post subject: Innocent Until Proven Guilty. Reply with quote

Do we yet know that the Reiser4 developers' code - or the kernel patches - really cause this zero-bytes problem?

Until the viper7 kernel I had no problems with the chilling occurrence of zero-byte files such as the gcc executable: one minute it's a real file; the next gcc is a bunch of zeroes. It's such an extraordinary bug.

After upgrading to the unstable udev the problems vanished; though I am not confident that this is the cure.

Until the Reiser4 developers enlighten us, I remain cautious.


Last edited by _pF_ on Sun Apr 29, 2007 9:05 pm; edited 1 time in total
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sun Apr 29, 2007 8:37 pm    Post subject: Re: Innocent Until Proven Guilty. Reply with quote

_pF_ wrote:
Do we yet know that the Reiser4 developers's code - or the kernel patches - really cause this zero-bytes problem?

Until the viper7 kernel I had no problems with the chilling occurrence of zero-byte files such as the gcc executable: one minute it's a real file; the next gcc is a bunch of zeroes. It's such an extraordinary bug.

After upgrading to the unstable udev the problems vanished; though I am not confident that this is the cure.

Until the Reiser4 developers enlighten us, I remain cautious.


I just encountered another attack of the "partial conversion" error :D

I couldn't copy the messages, but photographed it with my digicam, there really seems to be something wrong with the default/standard 'plugin'

write_sd_by_inode_common_(fs/reiser4/plugin/file_plugin_common.c:34)[nikita-2221]
WARNING: Failed to save sd for ...: -2
extent2tail (fs/reiser4/plugin/file/tail_conversion.c:712)[nikita-2202]
WARNING: Partial conversion of ...: 0 of 1: -2
release_unix_file (fs/reiser4/plugin/file/file.c:2383)[nikita-3233]
WARNING: Failed (-2) to convert in release_unix_file (150913)
reiser4[su(...)]: key_warning (fs/reiser4/plugin/file_plugin_common.c:34)[nikita-2221]


...
reiser4[login(...)]: traverse_tree (fs/reiser4/search.c:722)[nikita-373]:
WARNING: reiser-2018: Too many iterations. Tree corrupt, or (less likely) starvation occuring.: de:write, bias:exact


in syslog-ng I get lots of:

reiser4[agetty(2338)]: cbk_level_lookup(fs/reiser4/search.c:961[vs-3533]
WARNING: Keys are inconsistent. Fsck?


reiser4[sh(...)]: parse_node40 (fs/reiser4/plugin/node/node40.c:672)[nikita-494]

ok, that should be the most important parts (typed in everything)

the starvation part is pretty interesting, this time it happened when scanning another partition (windows) with clamav, so virtually no heavy I/O occured on the reiser4 partition, I think I'm going to post this sniplet on the reiser mailing list later:

reiser4 has problems with 2.6.21 in standard plugin-mode, but seems to work fine with cryptcompress, anyone willing to try out reiser4 with ingosched + 2.6.21? perhaps it's due to staircase deadline ...

I'm not sure but I think those problems start(ed) with a kernel greater than 2.6.21-rc7, 2.6.21-rc7 seemed to work ok if I recall right ...

update:

this unfortunately also happens with cryptcompress (this time also from within console, no X) :(

when scanning the windows partition I first get:

dir: reading directory.: Input/output error

then
'Segmentation fault'

after that

bash: no file or directory
(or similar messages)

if I launch dmesg I get:

parse_node40(fs/reiser4/plugin/node/node40.c:672)[nikita-494]:
WARNING:wrong level found in node: 1 != 2

or 2 != 1

... that's enough for now:

I'm out, I've switched to reiserfs for root, still using reiser4 with cryptcompress on /usr/portage, but as I already wrote on some other thread:

reiser4 seems to pretty fragile lately when it comes to use on /root partitions ...

*sigh*

I'll switch back, when it's more stable again ...
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa

Hardcore Gentoo Linux user since 2004 :D
Back to top
View user's profile Send private message
eiffel
n00b
n00b


Joined: 14 Feb 2006
Posts: 21
Location: Znojmo, CZ

PostPosted: Sun Apr 29, 2007 10:08 pm    Post subject: Reply with quote

on my amd64 system...
Pikachu linux # make
CHK include/linux/version.h
CHK include/linux/utsrelease.h
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
CC arch/x86_64/kernel/asm-offsets.s
GEN include/asm-x86_64/asm-offsets.h
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/kallsyms
HOSTCC scripts/pnmtologo
HOSTCC scripts/bin2c
CC init/main.o
CHK include/linux/compile.h
dnsdomainname: Unknown host
UPD include/linux/compile.h
CC init/version.o
CC init/do_mounts.o
CC init/do_mounts_rd.o
LD init/mounts.o
CC init/noinitramfs.o
CC init/calibrate.o
LD init/built-in.o
LD usr/built-in.o
CC arch/x86_64/kernel/process.o
CC arch/x86_64/kernel/signal.o
AS arch/x86_64/kernel/entry.o
CC arch/x86_64/kernel/traps.o
CC arch/x86_64/kernel/irq.o
CC arch/x86_64/kernel/ptrace.o
CC arch/x86_64/kernel/time.o
CC arch/x86_64/kernel/ioport.o
CC arch/x86_64/kernel/ldt.o
CC arch/x86_64/kernel/setup.o
CC arch/x86_64/kernel/i8259.o
CC arch/x86_64/kernel/sys_x86_64.o
CC arch/x86_64/kernel/x8664_ksyms.o
CC arch/x86_64/kernel/i387.o
CC arch/x86_64/kernel/syscall.o
CC arch/x86_64/kernel/vsyscall.o
CC arch/x86_64/kernel/setup64.o
CC arch/x86_64/kernel/../../i386/kernel/alternative.o
CC arch/x86_64/kernel/../../i386/kernel/bootflag.o
CC arch/x86_64/kernel/../../i386/kernel/cpuid.o
CC arch/x86_64/kernel/../../i386/kernel/i8237.o
CC arch/x86_64/kernel/../../i386/kernel/cpu/intel_cacheinfo.o
CC arch/x86_64/kernel/../../i386/kernel/msr.o
CC arch/x86_64/kernel/../../i386/kernel/pcspeaker.o
CC arch/x86_64/kernel/../../i386/kernel/quirks.o
CC arch/x86_64/kernel/../../i386/kernel/cpu/mcheck/therm_throt.o
CC arch/x86_64/kernel/../../i386/kernel/topology.o
LD arch/x86_64/kernel/bootflag.o
CC arch/x86_64/kernel/e820.o
CC arch/x86_64/kernel/reboot.o
LD arch/x86_64/kernel/quirks.o
LD arch/x86_64/kernel/i8237.o
CC arch/x86_64/kernel/pci-dma.o
CC arch/x86_64/kernel/pci-nommu.o
LD arch/x86_64/kernel/alternative.o
CC arch/x86_64/kernel/hpet.o
CC arch/x86_64/kernel/tsc.o
CC arch/x86_64/kernel/mce.o
LD arch/x86_64/kernel/therm_throt.o
CC arch/x86_64/kernel/mce_intel.o
CC arch/x86_64/kernel/mce_amd.o
CC arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/main.o
CC arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/if.o
CC arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/generic.o
CC arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/state.o
LD arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/built-in.o
CC arch/x86_64/kernel/acpi/../../../i386/kernel/acpi/boot.o
CC arch/x86_64/kernel/acpi/../../../i386/kernel/acpi/processor.o
CC arch/x86_64/kernel/acpi/../../../i386/kernel/acpi/cstate.o
LD arch/x86_64/kernel/acpi/boot.o
CC arch/x86_64/kernel/acpi/sleep.o
AS arch/x86_64/kernel/acpi/wakeup.o
LD arch/x86_64/kernel/acpi/processor.o
LD arch/x86_64/kernel/acpi/built-in.o
CC arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.o
CC arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/powernow-k8.o
LD arch/x86_64/kernel/cpufreq/powernow-k8.o
LD arch/x86_64/kernel/cpufreq/acpi-cpufreq.o
LD arch/x86_64/kernel/cpufreq/built-in.o
LD arch/x86_64/kernel/msr.o
LD arch/x86_64/kernel/cpuid.o
CC arch/x86_64/kernel/apic.o
CC arch/x86_64/kernel/nmi.o
CC arch/x86_64/kernel/io_apic.o
CC arch/x86_64/kernel/mpparse.o
CC arch/x86_64/kernel/genapic.o
CC arch/x86_64/kernel/genapic_cluster.o
CC arch/x86_64/kernel/genapic_flat.o
CC arch/x86_64/kernel/suspend.o
AS arch/x86_64/kernel/suspend_asm.o
CC arch/x86_64/kernel/early_printk.o
CC arch/x86_64/kernel/pmtimer.o
CC arch/x86_64/kernel/k8.o
CC arch/x86_64/kernel/module.o
CC arch/x86_64/kernel/early-quirks.o
arch/x86_64/kernel/early-quirks.c: In function 'intel_bugs':
arch/x86_64/kernel/early-quirks.c:76: warning: unused variable 'device'
LD arch/x86_64/kernel/topology.o
LD arch/x86_64/kernel/intel_cacheinfo.o
LD arch/x86_64/kernel/pcspeaker.o
LD arch/x86_64/kernel/built-in.o
AS arch/x86_64/kernel/head.o
CC arch/x86_64/kernel/head64.o
CC arch/x86_64/kernel/init_task.o
LDS arch/x86_64/kernel/vmlinux.lds
CC arch/x86_64/mm/init.o
CC arch/x86_64/mm/fault.o
CC arch/x86_64/mm/ioremap.o
CC arch/x86_64/mm/extable.o
CC arch/x86_64/mm/pageattr.o
CC arch/x86_64/mm/mmap.o
CC arch/x86_64/mm/../../i386/mm/hugetlbpage.o
LD arch/x86_64/mm/hugetlbpage.o
LD arch/x86_64/mm/built-in.o
LD arch/x86_64/crypto/built-in.o
AS arch/x86_64/ia32/ia32entry.o
CC arch/x86_64/ia32/sys_ia32.o
CC arch/x86_64/ia32/ia32_signal.o
CC arch/x86_64/ia32/tls32.o
CC arch/x86_64/ia32/ia32_binfmt.o
CC arch/x86_64/ia32/fpu32.o
CC arch/x86_64/ia32/ptrace32.o
CC arch/x86_64/ia32/syscall32.o
AS arch/x86_64/ia32/vsyscall-sysenter.o
SYSCALL arch/x86_64/ia32/vsyscall-sysenter.so
AS arch/x86_64/ia32/vsyscall-syscall.o
SYSCALL arch/x86_64/ia32/vsyscall-syscall.so
AS arch/x86_64/ia32/syscall32_syscall.o
CC arch/x86_64/ia32/mmap32.o
CC arch/x86_64/ia32/ipc32.o
CC arch/x86_64/ia32/ia32_aout.o
LD arch/x86_64/ia32/built-in.o
CC kernel/sched.o
CC kernel/fork.o
CC kernel/exec_domain.o
CC kernel/panic.o
CC kernel/printk.o
CC kernel/profile.o
CC kernel/exit.o
CC kernel/itimer.o
CC kernel/time.o
CC kernel/softirq.o
CC kernel/resource.o
CC kernel/sysctl.o
CC kernel/capability.o
CC kernel/ptrace.o
CC kernel/timer.o
CC kernel/user.o
CC kernel/signal.o
CC kernel/sys.o
CC kernel/kmod.o
CC kernel/workqueue.o
CC kernel/pid.o
CC kernel/extable.o
CC kernel/params.o
CC kernel/posix-timers.o
CC kernel/kthread.o
CC kernel/wait.o
CC kernel/kfifo.o
CC kernel/sys_ni.o
CC kernel/posix-cpu-timers.o
CC kernel/mutex.o
CC kernel/hrtimer.o
CC kernel/rwsem.o
CC kernel/latency.o
CC kernel/nsproxy.o
CC kernel/rcupdate.o
CC kernel/srcu.o
CC kernel/irq/handle.o
CC kernel/irq/manage.o
CC kernel/irq/spurious.o
CC kernel/irq/resend.o
CC kernel/irq/chip.o
CC kernel/irq/devres.o
CC kernel/irq/autoprobe.o
CC kernel/irq/proc.o
LD kernel/irq/built-in.o
CC kernel/power/main.o
CC kernel/power/process.o
CC kernel/power/console.o
CC kernel/power/pm.o
kernel/power/pm.c:205: warning: 'pm_register' is deprecated (declared at kernel/power/pm.c:64)
kernel/power/pm.c:205: warning: 'pm_register' is deprecated (declared at kernel/power/pm.c:64)
kernel/power/pm.c:206: warning: 'pm_send_all' is deprecated (declared at kernel/power/pm.c:180)
kernel/power/pm.c:206: warning: 'pm_send_all' is deprecated (declared at kernel/power/pm.c:180)
CC kernel/power/snapshot.o
CC kernel/power/suspend_builtin.o
CC kernel/power/modules.o
CC kernel/power/sysfs.o
CC kernel/power/suspend.o
CC kernel/power/io.o
CC kernel/power/pagedir.o
CC kernel/power/prepare_image.o
CC kernel/power/extent.o
CC kernel/power/pageflags.o
CC kernel/power/ui.o
kernel/power/ui.c: In function 'suspend_early_boot_message':
kernel/power/ui.c:80: warning: unused variable 'orig_loglevel'
kernel/power/ui.c:79: warning: unused variable 'continue_req'
kernel/power/ui.c:79: warning: unused variable 'orig_state'
CC kernel/power/power_off.o
CC kernel/power/atomic_copy.o
CC kernel/power/storage.o
CC kernel/power/netlink.o
kernel/power/netlink.c: In function 'netlink_prepare':
kernel/power/netlink.c:281: warning: passing argument 4 of 'netlink_kernel_create' from incompatible pointer type
kernel/power/netlink.c:281: error: too few arguments to function 'netlink_kernel_create'
make[2]: *** [kernel/power/netlink.o] Error 1
make[1]: *** [kernel/power] Error 2
make: *** [kernel] Error 2

_________________
AMD Turion 64 ML-28, 768MB RAM, 40GB HDD, ATI x200, WiFi Atheros IEEE802.11a/b/g - Gentoo 2006.1 amd64
screenshot update 11.1.2007
Back to top
View user's profile Send private message
Pse
Apprentice
Apprentice


Joined: 01 Mar 2005
Posts: 188
Location: by the plate river

PostPosted: Mon Apr 30, 2007 5:40 am    Post subject: Re: Innocent Until Proven Guilty. Reply with quote

kernelOfTruth wrote:

(...)
... that's enough for now:

I'm out, I've switched to reiserfs for root, still using reiser4 with cryptcompress on /usr/portage, but as I already wrote on some other thread:

reiser4 seems to pretty fragile lately when it comes to use on /root partitions ...

*sigh*

I'll switch back, when it's more stable again ...

I've already switched root to ext4 with 'insane' settings. For normal desktop usage, there isn't really much difference, but I did notice something that really favors R4: disk usage climbed from 4.2GiB to 5.2GiB. This obviously has to do with the fact that I keep /usr/portage, /var, and /etc on the same partition, but, hell, I just lost a Gig to nothing! Ah, well, I'll keep a spare partition with R4 + Cryptcompress (thanks for the info, kOT) and run .20 for awhile.
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Mon Apr 30, 2007 2:14 pm    Post subject: Re: Innocent Until Proven Guilty. Reply with quote

Pse wrote:
kernelOfTruth wrote:

(...)
... that's enough for now:

I'm out, I've switched to reiserfs for root, still using reiser4 with cryptcompress on /usr/portage, but as I already wrote on some other thread:

reiser4 seems to pretty fragile lately when it comes to use on /root partitions ...

*sigh*

I'll switch back, when it's more stable again ...

I've already switched root to ext4 with 'insane' settings. For normal desktop usage, there isn't really much difference, but I did notice something that really favors R4: disk usage climbed from 4.2GiB to 5.2GiB. This obviously has to do with the fact that I keep /usr/portage, /var, and /etc on the same partition, but, hell, I just lost a Gig to nothing! Ah, well, I'll keep a spare partition with R4 + Cryptcompress (thanks for the info, kOT) and run .20 for awhile.

Maybe you could try compressing ext4 as well.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
Pse
Apprentice
Apprentice


Joined: 01 Mar 2005
Posts: 188
Location: by the plate river

PostPosted: Mon Apr 30, 2007 3:10 pm    Post subject: Re: Innocent Until Proven Guilty. Reply with quote

vipernicus wrote:
Pse wrote:
kernelOfTruth wrote:

(...)
... that's enough for now:

I'm out, I've switched to reiserfs for root, still using reiser4 with cryptcompress on /usr/portage, but as I already wrote on some other thread:

reiser4 seems to pretty fragile lately when it comes to use on /root partitions ...

*sigh*

I'll switch back, when it's more stable again ...

I've already switched root to ext4 with 'insane' settings. For normal desktop usage, there isn't really much difference, but I did notice something that really favors R4: disk usage climbed from 4.2GiB to 5.2GiB. This obviously has to do with the fact that I keep /usr/portage, /var, and /etc on the same partition, but, hell, I just lost a Gig to nothing! Ah, well, I'll keep a spare partition with R4 + Cryptcompress (thanks for the info, kOT) and run .20 for awhile.

Maybe you could try compressing ext4 as well.


I'm sorry, I meant I lost 1GiB going from an uncompressed R4 partition to an ext4 one. I'll still look into compressing ext4, I wasn't aware you could do that 8O
Back to top
View user's profile Send private message
predatorfreak
l33t
l33t


Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.

PostPosted: Mon Apr 30, 2007 3:17 pm    Post subject: Re: Innocent Until Proven Guilty. Reply with quote

Pse wrote:
vipernicus wrote:
Pse wrote:
kernelOfTruth wrote:

(...)
... that's enough for now:

I'm out, I've switched to reiserfs for root, still using reiser4 with cryptcompress on /usr/portage, but as I already wrote on some other thread:

reiser4 seems to pretty fragile lately when it comes to use on /root partitions ...

*sigh*

I'll switch back, when it's more stable again ...

I've already switched root to ext4 with 'insane' settings. For normal desktop usage, there isn't really much difference, but I did notice something that really favors R4: disk usage climbed from 4.2GiB to 5.2GiB. This obviously has to do with the fact that I keep /usr/portage, /var, and /etc on the same partition, but, hell, I just lost a Gig to nothing! Ah, well, I'll keep a spare partition with R4 + Cryptcompress (thanks for the info, kOT) and run .20 for awhile.

Maybe you could try compressing ext4 as well.


I'm sorry, I meant I lost 1GiB going from an uncompressed R4 partition to an ext4 one. I'll still look into compressing ext4, I wasn't aware you could do that 8O


There's a ton of FUSE compression overlays. I'm partial to fusecompress, because it gets decent compression with gzip and doesn't have the horrible-ass-performance of compfused.

Edit: Some numbers to backup my claims: My normal kernel tree is about ~300MB, using fusecompress with gzip, I got it to ~159MB. That is a pretty significant savings (141MB!). I haven't tested it on anything else yet, but I'll definitely be using it for my /usr/src from now on. If I ran Gentoo, I'd DEFINITELY have fusecompress with gzip on /usr/portage as well, because I'd bet the savings will be even more significant.

Edit 2: Even more numbers: On Arch, my /var/abs was about 490MB before doing rm -rf /var/abs, mkdir /var/.cf_abs, /usr/bin/fusecompress -o allow_other -c gz /var/.cf_abs /var/abs; abs (recheckout the entire thing), without my local stuff, it comes out to 45MB!
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.


Last edited by predatorfreak on Mon Apr 30, 2007 3:50 pm; edited 1 time in total
Back to top
View user's profile Send private message
Pse
Apprentice
Apprentice


Joined: 01 Mar 2005
Posts: 188
Location: by the plate river

PostPosted: Mon Apr 30, 2007 3:48 pm    Post subject: Re: Innocent Until Proven Guilty. Reply with quote

predatorfreak wrote:
Pse wrote:
vipernicus wrote:
Pse wrote:
kernelOfTruth wrote:

(...)
... that's enough for now:

I'm out, I've switched to reiserfs for root, still using reiser4 with cryptcompress on /usr/portage, but as I already wrote on some other thread:

reiser4 seems to pretty fragile lately when it comes to use on /root partitions ...

*sigh*

I'll switch back, when it's more stable again ...

I've already switched root to ext4 with 'insane' settings. For normal desktop usage, there isn't really much difference, but I did notice something that really favors R4: disk usage climbed from 4.2GiB to 5.2GiB. This obviously has to do with the fact that I keep /usr/portage, /var, and /etc on the same partition, but, hell, I just lost a Gig to nothing! Ah, well, I'll keep a spare partition with R4 + Cryptcompress (thanks for the info, kOT) and run .20 for awhile.

Maybe you could try compressing ext4 as well.


I'm sorry, I meant I lost 1GiB going from an uncompressed R4 partition to an ext4 one. I'll still look into compressing ext4, I wasn't aware you could do that 8O


There's a ton of FUSE compression overlays. I'm partial to fusecompress, because it gets decent compression with gzip and doesn't have the horrible-ass-performance of compfused.

Edit: Some numbers to backup my claims: My normal kernel tree is about ~300MB, using fusecompress with gzip, I got it to ~159MB. That is a pretty significant savings (241MB!). I haven't tested it on anything else yet, but I'll definitely be using it for my /usr/src from now on. If I ran Gentoo, I'd DEFINITELY have fusecompress with gzip on /usr/portage as well, because I'd bet the savings will be even more significant.

Do you have any numbers regarding its performance? How about data integrity, have you had any problems? What version are you running? We should start a new thread, this is a bit off-topic. BTW, it should be '141MB' :)
Back to top
View user's profile Send private message
predatorfreak
l33t
l33t


Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.

PostPosted: Mon Apr 30, 2007 3:54 pm    Post subject: Re: Innocent Until Proven Guilty. Reply with quote

Pse wrote:
Do you have any numbers regarding its performance? How about data integrity, have you had any problems? What version are you running? We should start a new thread, this is a bit off-topic. BTW, it should be '141MB' :)


Honest typo, sorry. Can't say much for data integrity just yet, but I highly doubt that it would clobber anything. The performance of fusecompress is very good, it takes a bit more time to write (especially for large files) to a fusecompress'd directory, but this is to be expected (it comes with the overhead of compression), read performance feels about equal. The performance of compFUSEd wasn't so good, with gzip it got better compression rates in most cases, but suffered from excessively bad write times (I'd say maybe ~30-40 seconds worse on my copy-your-giant-kernel-tree test), it also seems to lack anyway of setting fuse mount options, so I could only get it to allow one user access at a time. Currently, I'm using fusecompress 1.99.13.

Suppose this discussion could be split off.
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.
Back to top
View user's profile Send private message
yngwin
Retired Dev
Retired Dev


Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China

PostPosted: Mon Apr 30, 2007 8:52 pm    Post subject: Reply with quote

I can't seem to compile vmware-modules with this kernel:
Code:
 * Preparing vmnet module
Using 2.6.x kernel build system.
make -C /usr/src/linux/include/.. M=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.21-ragnarok1'
make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/driver.o
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/hub.o
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.o
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.c: In function ‘VNetCopyDatagramToUser’:
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.c:633: error: ‘const struct sk_buff’ has no member named ‘h’
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.c:633: error: ‘const struct sk_buff’ has no member named ‘nh’
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.c:639: error: ‘const struct sk_buff’ has no member named ‘h’
make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.o] Error 1
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only] Error 2
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.21-ragnarok1'
make: *** [vmnet.ko] Error 2

!!! ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  ebuild.sh, line 1304:   Called linux-mod_src_compile
  linux-mod.eclass, line 516:   Called die

!!! Unable to make   auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.21-ragnarok1/build.


Anyone any idea what's up with that?
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Mon Apr 30, 2007 9:22 pm    Post subject: Reply with quote

yngwin wrote:
I can't seem to compile vmware-modules with this kernel:
Code:
 * Preparing vmnet module
Using 2.6.x kernel build system.
make -C /usr/src/linux/include/.. M=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.21-ragnarok1'
make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/driver.o
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/hub.o
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.o
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.c: In function ‘VNetCopyDatagramToUser’:
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.c:633: error: ‘const struct sk_buff’ has no member named ‘h’
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.c:633: error: ‘const struct sk_buff’ has no member named ‘nh’
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.c:639: error: ‘const struct sk_buff’ has no member named ‘h’
make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.o] Error 1
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only] Error 2
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.21-ragnarok1'
make: *** [vmnet.ko] Error 2

!!! ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  ebuild.sh, line 1304:   Called linux-mod_src_compile
  linux-mod.eclass, line 516:   Called die

!!! Unable to make   auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.21-ragnarok1/build.


Anyone any idea what's up with that?

layman -a vmware ?
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
yngwin
Retired Dev
Retired Dev


Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China

PostPosted: Mon Apr 30, 2007 10:01 pm    Post subject: Reply with quote

vipernicus wrote:
layman -a vmware ?

I was actually using that. But overlay or official tree, and different versions, they all lead to the same error.
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Mon Apr 30, 2007 10:16 pm    Post subject: Reply with quote

yngwin wrote:
vipernicus wrote:
layman -a vmware ?

I was actually using that. But overlay or official tree, and different versions, they all lead to the same error.


for me too :(
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa

Hardcore Gentoo Linux user since 2004 :D
Back to top
View user's profile Send private message
yngwin
Retired Dev
Retired Dev


Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China

PostPosted: Mon Apr 30, 2007 11:40 pm    Post subject: Reply with quote

I've been experimenting a bit, and I'm thinking it's the git patch which causes trouble. I'll try something else still, then maybe make a non-git release.

Update: with a 2.6.21.1 based kernel (instead of -git2 or -git3) I can compile vmware-modules, but as soon as I start up vmware-player it hardlocks my system. So that's not very helpful...

Update2: apparently the problem was a faulty vmware-image, and so I can present you -ragnarok2 :D
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
xy
n00b
n00b


Joined: 08 May 2007
Posts: 1

PostPosted: Tue May 08, 2007 8:35 pm    Post subject: vmware-modules ebuild fails Reply with quote

yngwin wrote:
I've been experimenting a bit, and I'm thinking it's the git patch which causes trouble. I'll try something else still, then maybe make a non-git release.

Update: with a 2.6.21.1 based kernel (instead of -git2 or -git3) I can compile vmware-modules, but as soon as I start up vmware-player it hardlocks my system. So that's not very helpful...

Update2: apparently the problem was a faulty vmware-image, and so I can present you -ragnarok2 :D


I am searching for advice concerning this error as well (!!! ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed). My output appears the same. I'm using a much older kernel (2.6.13-gentoo-r5). Is there any chance of getting vmware-modules to build with this older kernel?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum