search for: neakum

Just now I ran tune2fs -j on the root filesystem of a box running 2.6.0-test8. Then I edited /etc/fstab and changed the FS type to from ext2 to ext3, saved the file, and invoked vim on the file again. A few moments after this, the box hung. Unfortunately X was running at the time, and so I don't have any messages to cite. Is this a known problem?

Hi, We have recently switched from XFS to ext3 do to various corruption scenarios that were witnessed. Does ext3 have something like xfs_growfs for growing the FS to the end of the underlying partition? Thanks, Menny

Hi, I try to convert my RedHat 7.3. partitions from ext3 to ext2. I have found a thread dealing with this issue. Thus: "tune2fs -O ^has_journal /dev/foo" and "e2fsck /dev/foo" will do the magic! This works fine for "/boot" but when I try to convert "/" my kernel panics? The kernel panics message appears shortly after the attempt to startup kjournald. How

I accidentally removed an ext3 partition from the partition table. I know roughly where it started. Is there any way of finding the superblock and reconstructing it? TIA, Dave (Yes I have a backup of the important stuff!)

i have a question on ext3 modes and am not sure if this list is still active

..._journal_head+100/140> 1c: 90 12 22 b0 or %o0, 0x2b0, %o0 Code; 0049da64 <__journal_remove_journal_head+104/140> 20: 92 12 63 f0 or %o1, 0x3f0, %o1 1 warning issued. Results may not be reliable. -- ///////////////// | | The spark of a pin <sneakums@zork.net> | (require 'gnu) | dropping, falling feather-like. \\\\\\\\\\\\\\\\\ | | There is too much noise.

I have a few settings that change based on the network that a system is in, and I have a heterogeneous collection of networks (a few /24s, some /25s, a /29 and a couple /27s, and hey look a /16 in rfc1918 space and...). So I can''t do simple regex matches on dotted-quad IP notation and expect to get a complete story. What I''d like is something like, I dunno... $nameserver =

http://projects.puppetlabs.com/issues/7612 The exported resources syntax: @@user { luke: ensure => present } Is concise and powerful, but very difficult to read. We should consider word-based syntax, e.g.: export @user { luke: ensure => present } And taking into account #7605, perhaps: export virtual user { luke: ensure => present } Please comment on the ticket or reply

...#39;s been a slow week. [1] For this read: "tried to match rejects to pieces of code". I don't know anything about the ext3 code, but that's okay: I don't know anything about the Linux code, either. -- ///////////////// | | The spark of a pin <sneakums@zork.net> | (require 'gnu) | dropping, falling feather-like. \\\\\\\\\\\\\\\\\ | | There is too much noise.