From sheelraj at gmail.com Mon Dec 1 19:59:31 2008 From: sheelraj at gmail.com (Sheel Raj) Date: Mon, 1 Dec 2008 14:59:31 -0500 Subject: EXT3 filesystem data mode Message-ID: <4eca88550812011159u362f12b9vb12f7d7fd7a4cd9a@mail.gmail.com> Hi all Here's my 2 questions about linux ext3 filesystem 1. How do I identify which data mode[writeback, ordered. journal] is being used by the filesystem on my machine. I checked /etc/fstab and /etc/log/messages and could not get any info from there. I know 'tune2fs' can be used to set the modes, but I would like to know which mode is it in, before setting up any. 2. In either of the data modes, which method or utility would you suggest to secure erase/delete files and directories, so that they are not recovered by any means. Any reply, reference regarding my questions will be appreciated. Thanks in advance Sheel Raj From bruno at wolff.to Mon Dec 1 22:12:38 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Mon, 1 Dec 2008 16:12:38 -0600 Subject: EXT3 filesystem data mode In-Reply-To: <4eca88550812011159u362f12b9vb12f7d7fd7a4cd9a@mail.gmail.com> References: <4eca88550812011159u362f12b9vb12f7d7fd7a4cd9a@mail.gmail.com> Message-ID: <20081201221238.GA26285@wolff.to> On Mon, Dec 01, 2008 at 14:59:31 -0500, Sheel Raj wrote: > Hi all > > Here's my 2 questions about linux ext3 filesystem > > 1. How do I identify which data mode[writeback, ordered. journal] is > being used by the filesystem on my machine. > I checked /etc/fstab and /etc/log/messages and could not get any info > from there. I know 'tune2fs' can be used to set the modes, but I would > like to know which mode is it in, before setting up any. tune2fs -l device will show you the defaults. cat /proc/mounts will show you the mount options. > 2. In either of the data modes, which method or utility would you > suggest to secure erase/delete files and directories, so that they are > not recovered by any means. Use a rescue disk to boot without using the disks and write /dev/urandom over the the raw device. Pull out the disks and incinerate them. Smash the remains up with a sledge hammer. Be sure to get rid of any back ups you have and any people that know the conents as well. From ro1208984 at gmail.com Tue Dec 2 13:49:39 2008 From: ro1208984 at gmail.com (milos rovcanin) Date: Tue, 2 Dec 2008 14:49:39 +0100 Subject: bit per bit copy! ext3 Message-ID: <537d0ac00812020549h27fa2cd7h399c433b487bf855@mail.gmail.com> I have a flash memory stick that is formated with ext3 file system. NOw, there is an application on it that I would like to copy to another memory stick. I can copy it, but when I do so, that application does not work properly (it won't start - boot problem???). Is there a tool that can copy an entire content from one flash stick to another? Thanks!!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpiszcz at lucidpixels.com Tue Dec 2 13:55:17 2008 From: jpiszcz at lucidpixels.com (Justin Piszcz) Date: Tue, 2 Dec 2008 08:55:17 -0500 (EST) Subject: bit per bit copy! ext3 In-Reply-To: <537d0ac00812020549h27fa2cd7h399c433b487bf855@mail.gmail.com> References: <537d0ac00812020549h27fa2cd7h399c433b487bf855@mail.gmail.com> Message-ID: On Tue, 2 Dec 2008, milos rovcanin wrote: > I have a flash memory stick that is formated with ext3 file system. NOw, > there is an application on it that I would like to copy to another memory > stick. I can copy it, but when I do so, that application does not work > properly (it won't start - boot problem???). Is there a tool that can copy > an entire content from one flash stick to another? Thanks!!! > use dd dd if=/dev/sda of=/dev/sdb or # original flash dd if=/dev/sda of=flash_disk.img # with second flash flugged in dd if=flash_disk.img of=/dev/sda They must/should be the same sizes though. Justin. From alex at alex.org.uk Tue Dec 2 14:01:56 2008 From: alex at alex.org.uk (Alex Bligh) Date: Tue, 02 Dec 2008 14:01:56 +0000 Subject: bit per bit copy! ext3 In-Reply-To: References: <537d0ac00812020549h27fa2cd7h399c433b487bf855@mail.gmail.com> Message-ID: <5C96EA8A781A1E0B1E65F42E@Ximines.local> --On 2 December 2008 08:55:17 -0500 Justin Piszcz wrote: ># original flash > dd if=/dev/sda of=flash_disk.img ># with second flash flugged in > dd if=flash_disk.img of=/dev/sda > > They must/should be the same sizes though. I believe if you are copying the whole of sda, a larger destination disk will not be problematic. Alex From jpiszcz at lucidpixels.com Tue Dec 2 14:14:17 2008 From: jpiszcz at lucidpixels.com (Justin Piszcz) Date: Tue, 2 Dec 2008 09:14:17 -0500 (EST) Subject: bit per bit copy! ext3 In-Reply-To: <5C96EA8A781A1E0B1E65F42E@Ximines.local> References: <537d0ac00812020549h27fa2cd7h399c433b487bf855@mail.gmail.com> <5C96EA8A781A1E0B1E65F42E@Ximines.local> Message-ID: On Tue, 2 Dec 2008, Alex Bligh wrote: > > > --On 2 December 2008 08:55:17 -0500 Justin Piszcz > wrote: > >> # original flash >> dd if=/dev/sda of=flash_disk.img >> # with second flash flugged in >> dd if=flash_disk.img of=/dev/sda >> >> They must/should be the same sizes though. > > I believe if you are copying the whole of sda, a larger destination disk > will not be problematic. > > Alex > Alex, this is true but I have seen/done this before example: 80GB DD/Acronis => 500GB disk (albeit this was windows).. It showed up as an 80 gigabyte disk/etc on the new hard drive even though it had additional capacity available. So yeah it should work, just don't count on being able to use the space, in my case/example there was an encryption/disk product involved and dd was the only way to move the data and if you tried to expand the partition inside of the encryption product it would crash the machine/windows would not boot correctly, etc. Justin. From alex at alex.org.uk Tue Dec 2 14:49:26 2008 From: alex at alex.org.uk (Alex Bligh) Date: Tue, 02 Dec 2008 14:49:26 +0000 Subject: bit per bit copy! ext3 In-Reply-To: References: <537d0ac00812020549h27fa2cd7h399c433b487bf855@mail.gmail.com> <5C96EA8A781A1E0B1E65F42E@Ximines.local> Message-ID: <444767F8794D41CD7ADF24B2@Ximines.local> --On 2 December 2008 09:14:17 -0500 Justin Piszcz wrote: > 80GB DD/Acronis => 500GB disk (albeit this was windows).. > > It showed up as an 80 gigabyte disk/etc on the new hard drive even though > it had additional capacity available. Yes, that's what will happen. dd will not of itself expand the filesystem to match the available space. If the device is partitioned, you may be able to just copy the partition and be left with some free space. Alex From darkonc at gmail.com Tue Dec 2 16:21:03 2008 From: darkonc at gmail.com (Stephen Samuel) Date: Tue, 2 Dec 2008 08:21:03 -0800 Subject: bit per bit copy! ext3 In-Reply-To: References: <537d0ac00812020549h27fa2cd7h399c433b487bf855@mail.gmail.com> Message-ID: <6cd50f9f0812020821p4b8ca996w504bb12df6dceb9d@mail.gmail.com> I think, however, that you should actually copy /dev/sda1, to /dev/sdba1 not /dev/sda. to /dev/sdb If you copy /dev/sda1, you will also copy the partition table. If your flash drives are different sizes you might end up with problems. another solution would be, especially if you are making an intermediate copy on your hard drive, to use partimage. Partimage will only copy the sectors on the partition that are actually in use.. thus saving both disk space and time for the copy process. On Tue, Dec 2, 2008 at 5:55 AM, Justin Piszcz wrote: > > > On Tue, 2 Dec 2008, milos rovcanin wrote: > > I have a flash memory stick that is formated with ext3 file system. NOw, >> there is an application on it that I would like to copy to another memory >> stick. I can copy it, but when I do so, that application does not work >> properly (it won't start - boot problem???). Is there a tool that can >> copy >> an entire content from one flash stick to another? Thanks!!! >> >> > use dd > > dd if=/dev/sda of=/dev/sdb > > or > > # original flash > dd if=/dev/sda of=flash_disk.img > # with second flash flugged in > dd if=flash_disk.img of=/dev/sda > > They must/should be the same sizes though. > > Justin. > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users > -- Stephen Samuel http://www.bcgreen.com 778-861-7641 -------------- next part -------------- An HTML attachment was scrubbed... URL: From worleys at gmail.com Tue Dec 2 23:28:41 2008 From: worleys at gmail.com (Chris Worley) Date: Tue, 2 Dec 2008 16:28:41 -0700 Subject: Block Discard (Was Re: When is a block free?) Message-ID: I'm noticing in the latest 2.6.28 pre-patches at kernel.org, ext4 has a call to sb_issue_discard, but the call that was in David Woodhouse's ext2 branch is gone. Will only ext4 support "discards" going forward? Thanks, Chris On Wed, Oct 1, 2008 at 11:18 AM, Chris Worley wrote: > On Mon, Sep 29, 2008 at 10:39 AM, Theodore Tso wrote: > > On Mon, Sep 29, 2008 at 09:24:33AM -0600, Chris Worley wrote: > >> On Tue, Sep 16, 2008 at 3:32 PM, Chris Worley > wrote: > >> > For example, in balloc.c I'm seeing ext3_free_blocks_sb > >> > calls ext3_clear_bit_atomic at the bottom... is that when the block is > >> > freed? Are all blocks freed here? > >> > >> David Woodhouse, in an article at http://lwn.net/Articles/293658/, is > >> implementing the T10/T13 committees "Trim" request in 2.6.28 kernels. > >> > >> Would it be appropriate to call "blkdev_issue_discard" at the bottom > >> of ext3_free_blocks_sb where ext3_clear_bit_atomic is being called? > > > > Unfortunately, it's not as simple as that. The problem is that as > > soon as you call trim, the drive is allowed to discard the contents of > > that block so that future attempts to read from that block returns all > > zeros. Therefore we can't call Trim until after the transaction has > > committed. That means we have to keep a linked list of block extents > > that are to be trimmed attached to the commit object, and only send > > the trim requests once the commit block has been written to disk. > > > > It's on the ext4 developer's TODO list to add Trim support to ext3 and > > ext4. > > I was perusing David Woodhouse's 2.6.27-rc2 kernel at > git://git.infradead.org/users/drzeus/discard-2.6.git, and noticed he > has the discard built-in to where I was talking about for ext2... so I > coded our driver to handle discards, and it works very nicely!!! > > The journaling issue you raise is not a show-stopper on the block > device side: if the block device has to maintain a couple of blocks > that are not really in use, it's no big deal (eventually the blocks > will be re-written and the universe will be in order again)... for the > users, I can understand if the discard is preserved on the block > device, while the fs still thinks there's good data in there (we'll > give you back all zeros on read). > > Chris > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Manfred.KNOPS at 3ds.com Wed Dec 10 09:53:50 2008 From: Manfred.KNOPS at 3ds.com (Knops, Manfred) Date: Wed, 10 Dec 2008 10:53:50 +0100 Subject: unmeant redundant partitions Message-ID: <493F91AE.1080704@3ds.com> Hello, it's the first time for me to use a mailing group. So I hope it's the right place. At the moment I installed opensuse 11.0 on a machine with two harddiscs and one raid system with adaptec raid controller. I have installed linux on one harddisc before I build the raid combination. After that I rebooted the machine. At this moment the device id's changed. Now I have following harddisc's: fileserver:~ # fdisk -l WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 8996.8 GB, 8996872257536 bytes 255 heads, 63 sectors/track, 1093807 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 267350 2147483647+ ee EFI GPT Disk /dev/sdb: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x2e2e2e2e Device Boot Start End Blocks Id System /dev/sdb1 1 1045 8393931 82 Linux swap / Solaris /dev/sdb2 * 1046 30401 235802070 f W95 Ext'd (LBA) /dev/sdb5 1046 2351 10490413+ 83 Linux /dev/sdb6 2352 3004 5245191 83 Linux /dev/sdb7 3005 30401 220066371 83 Linux Disk /dev/sdc: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x2e2e2e2e Device Boot Start End Blocks Id System /dev/sdc1 1 1045 8393931 82 Linux swap / Solaris /dev/sdc2 * 1046 30401 235802070 f W95 Ext'd (LBA) /dev/sdc5 1046 2351 10490413+ 83 Linux /dev/sdc6 2352 3004 5245191 83 Linux /dev/sdc7 3005 30401 220066371 83 Linux Disk /dev/dm-0: 161.0 GB, 161037403136 bytes 255 heads, 63 sectors/track, 19578 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Most time I use partition labels to mount the partitions. I can't remember why. But the partitions of sdb and sdc have the same labels: fileserver:~ # !for for device in sdb5 sdc5 sdb6 sdc6 sdb7 sdc7; do tune2fs -l /dev/${device} | grep "Filesystem volume name"; done Filesystem volume name: rootOnSdb Filesystem volume name: rootOnSdb Filesystem volume name: tmpOnSdb Filesystem volume name: tmpOnSdb Filesystem volume name: varOnSdb Filesystem volume name: varOnSdb sdb is the default disc for linux. sdc should be a spare part. So this is the mount table: fileserver:~ # mount /dev/sdb5 on / type ext3 (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sdb6 on /tmp type ext3 (rw,acl,user_xattr) /dev/sdb7 on /var type ext3 (rw,acl,user_xattr) /dev/sda1 on /fileserverShare type ext3 (rw,acl,user_xattr) /dev/sda2 on /backup type ext3 (rw,acl,user_xattr) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) proc on /var/lib/ntp/proc type proc (ro) /dev/mapper/cr_sda3 on /home type ext3 (rw,acl,user_xattr) Now I will show you what I have found. 1. I touched a file on /root. / is the mountpoint of /dev/sdb5. So the file must be storage on /dev/sdb5. fileserver:~ # date Mi 10. Dez 10:34:03 CET 2008 fileserver:~ # echo `date` >> /root/foo.bar fileserver:~ # ls -l /root/foo.bar -rw-r--r-- 1 root root 29 2008-12-10 10:34 /root/foo.bar fileserver:~ # cat /root/foo.bar Mi 10. Dez 10:34:19 CET 2008 fileserver:~ # 2. I mount /dev/sdc5 to /local/sdc/ fileserver:~ # mount -v /local/sdc/ /dev/sdc5 on /local/sdc type ext3 (rw,acl,user_xattr) 3. I list the entry of /local/sdc/root/ fileserver:~ # ls -l /local/sdc/root/ total 92 -rw------- 1 root root 13431 2008-12-10 10:03 .bash_history drwxr-xr-x 2 root root 4096 2008-12-09 13:00 bin -rw-r--r-- 1 root root 1332 2005-11-23 17:06 .exrc -rw-r--r-- 1 root root 29 2008-12-10 10:34 foo.bar drwx------ 2 root root 4096 2008-12-05 11:47 .gnupg drwxr-xr-x 6 root root 4096 2008-12-05 10:56 inst-sys drwxr-xr-x 2 root root 4096 2008-12-05 11:20 .kbd drwxr-xr-x 2 root root 4096 2008-12-08 10:09 ldap_datenbank_sicherung -rw-r--r-- 1 root root 57 2008-12-08 16:32 .ldaprc -r-------- 1 root root 102 2008-12-09 11:17 Liesmich.txt drwx------ 2 root root 4096 2008-12-05 11:33 .ssh -rw-r--r-- 1 root root 20859 2008-12-05 11:34 .suse_register.log -rw------- 1 root root 9526 2008-12-10 09:44 .viminfo -rw------- 1 root root 0 2008-12-09 13:31 .Xauthority fileserver:~ # cat /local/sdc/root/foo.bar Mi 10. Dez 10:34:19 CET 2008 At this moment I was confused about the existing file foo.bar under /local/sdc/. Because I can't explain why it exists. First I think there was an error on my side. So I delete /local/sdc/root/foo.bar. fileserver:~ # rm -vf /local/sdc/root/foo.bar removed `/local/sdc/root/foo.bar' fileserver:~ # fileserver:~ # ls -l /local/sdc/root total 88 -rw------- 1 root root 13431 2008-12-10 10:03 .bash_history drwxr-xr-x 2 root root 4096 2008-12-09 13:00 bin -rw-r--r-- 1 root root 1332 2005-11-23 17:06 .exrc drwx------ 2 root root 4096 2008-12-05 11:47 .gnupg drwxr-xr-x 6 root root 4096 2008-12-05 10:56 inst-sys drwxr-xr-x 2 root root 4096 2008-12-05 11:20 .kbd drwxr-xr-x 2 root root 4096 2008-12-08 10:09 ldap_datenbank_sicherung -rw-r--r-- 1 root root 57 2008-12-08 16:32 .ldaprc -r-------- 1 root root 102 2008-12-09 11:17 Liesmich.txt drwx------ 2 root root 4096 2008-12-05 11:33 .ssh -rw-r--r-- 1 root root 20859 2008-12-05 11:34 .suse_register.log -rw------- 1 root root 9526 2008-12-10 09:44 .viminfo -rw------- 1 root root 0 2008-12-09 13:31 .Xauthority The file doesn't exist anymore on /local/sdc/root/. Now I check /root. fileserver:~ # ls -l /root/ total 88 -rw------- 1 root root 13431 2008-12-10 10:03 .bash_history drwxr-xr-x 2 root root 4096 2008-12-09 13:00 bin -rw-r--r-- 1 root root 1332 2005-11-23 17:06 .exrc drwx------ 2 root root 4096 2008-12-05 11:47 .gnupg drwxr-xr-x 6 root root 4096 2008-12-05 10:56 inst-sys drwxr-xr-x 2 root root 4096 2008-12-05 11:20 .kbd drwxr-xr-x 2 root root 4096 2008-12-08 10:09 ldap_datenbank_sicherung -rw-r--r-- 1 root root 57 2008-12-08 16:32 .ldaprc -r-------- 1 root root 102 2008-12-09 11:17 Liesmich.txt drwx------ 2 root root 4096 2008-12-05 11:33 .ssh -rw-r--r-- 1 root root 20859 2008-12-05 11:34 .suse_register.log -rw------- 1 root root 9526 2008-12-10 09:44 .viminfo -rw------- 1 root root 0 2008-12-09 13:31 .Xauthority The file foo.bar doesn't exist anymore here. But why? Can someone explain me what happens on this machine? Regards Manfred From lakshmipathi.g at gmail.com Mon Dec 15 05:14:47 2008 From: lakshmipathi.g at gmail.com (lakshmi pathi) Date: Mon, 15 Dec 2008 10:44:47 +0530 Subject: How to sell linux tools? Message-ID: Hi, I need clarifications on how to sell linux tools. (Though i' not sure how people ready to buy it :) ) I have written few tools and planning to write more(by giving up current non-linux & boring job). I want to know,which license will allow me to sell tools/softwares? (I hope to sell the products through online) Cheers, Lakshmipathi.G www.giis.co.in From tambewilliam at gmail.com Mon Dec 15 07:06:14 2008 From: tambewilliam at gmail.com (William Tambe) Date: Mon, 15 Dec 2008 01:06:14 -0600 Subject: How to sell linux tools? In-Reply-To: References: Message-ID: <494601E6.7000200@gmail.com> You know we like free stuff right? lakshmi pathi wrote: > Hi, > I need clarifications on how to sell linux tools. (Though i' not sure > how people ready to buy it :) ) > I have written few tools and planning to write more(by giving up > current non-linux & boring job). > I want to know,which license will allow me to sell tools/softwares? (I > hope to sell the products through online) > > Cheers, > Lakshmipathi.G > www.giis.co.in > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users > From lakshmipathi.g at gmail.com Mon Dec 15 07:10:27 2008 From: lakshmipathi.g at gmail.com (lakshmi pathi) Date: Mon, 15 Dec 2008 12:40:27 +0530 Subject: How to sell linux tools? In-Reply-To: <494601E6.7000200@gmail.com> References: <494601E6.7000200@gmail.com> Message-ID: Yes ....Even i like free stuffs :) ...But how could an Linux/open source programmer earn money for living? Cheers, Lakshmipathi.G On Mon, Dec 15, 2008 at 12:36 PM, William Tambe wrote: > You know we like free stuff right? > > lakshmi pathi wrote: >> >> Hi, >> I need clarifications on how to sell linux tools. (Though i' not sure >> how people ready to buy it :) ) >> I have written few tools and planning to write more(by giving up >> current non-linux & boring job). >> I want to know,which license will allow me to sell tools/softwares? (I >> hope to sell the products through online) >> >> Cheers, >> Lakshmipathi.G >> www.giis.co.in >> >> _______________________________________________ >> Ext3-users mailing list >> Ext3-users at redhat.com >> https://www.redhat.com/mailman/listinfo/ext3-users >> > -- Cheers, Lakshmipathi.G From tambewilliam at gmail.com Mon Dec 15 07:27:39 2008 From: tambewilliam at gmail.com (William Tambe) Date: Mon, 15 Dec 2008 01:27:39 -0600 Subject: How to sell linux tools? In-Reply-To: References: <494601E6.7000200@gmail.com> Message-ID: <494606EB.3090208@gmail.com> I don't know if this is the right discussion group for the subject, but I am also curious to know. ?-| lakshmi pathi wrote: > Yes ....Even i like free stuffs :) ...But how could an Linux/open > source programmer earn money for living? > > Cheers, > Lakshmipathi.G > > > On Mon, Dec 15, 2008 at 12:36 PM, William Tambe wrote: >> You know we like free stuff right? >> >> lakshmi pathi wrote: >>> Hi, >>> I need clarifications on how to sell linux tools. (Though i' not sure >>> how people ready to buy it :) ) >>> I have written few tools and planning to write more(by giving up >>> current non-linux & boring job). >>> I want to know,which license will allow me to sell tools/softwares? (I >>> hope to sell the products through online) >>> >>> Cheers, >>> Lakshmipathi.G >>> www.giis.co.in >>> >>> _______________________________________________ >>> Ext3-users mailing list >>> Ext3-users at redhat.com >>> https://www.redhat.com/mailman/listinfo/ext3-users >>> > > > From cax0cn at gmail.com Mon Dec 15 10:26:35 2008 From: cax0cn at gmail.com (Joseph Chen) Date: Mon, 15 Dec 2008 18:26:35 +0800 Subject: How to sell linux tools? In-Reply-To: <494606EB.3090208@gmail.com> References: <494601E6.7000200@gmail.com> <494606EB.3090208@gmail.com> Message-ID: <8d423b320812150226t60f141c1x6aff460ddd52cbe5@mail.gmail.com> Suppose Lakshmi is going to write ext3 or file-system related tools. Unless your software is really good and urgently needed by some small business groups, it's hard to sell linux software for money. When using choose, it means everything is freely available. I'd show m 0.02 here, hope to be helpful: 1, Have a Try with SaaS. Share your programming experience with some startups, and serve as an consultant. 2, Looking for freelance jobs on oDesk, eLance, there are some developing positions, and you can serve as a dedicated programmer as what you did. 3, Start your own opensource project if you know the linux market quite well.(I know that recovering data from a failed RAID or disk is a good market) All the best, Joseph On Mon, Dec 15, 2008 at 3:27 PM, William Tambe wrote: > I don't know if this is the right discussion group for the subject, but I > am also curious to know. ?-| > > > lakshmi pathi wrote: > >> Yes ....Even i like free stuffs :) ...But how could an Linux/open >> source programmer earn money for living? >> >> Cheers, >> Lakshmipathi.G >> >> >> On Mon, Dec 15, 2008 at 12:36 PM, William Tambe >> wrote: >> >>> You know we like free stuff right? >>> >>> lakshmi pathi wrote: >>> >>>> Hi, >>>> I need clarifications on how to sell linux tools. (Though i' not sure >>>> how people ready to buy it :) ) >>>> I have written few tools and planning to write more(by giving up >>>> current non-linux & boring job). >>>> I want to know,which license will allow me to sell tools/softwares? (I >>>> hope to sell the products through online) >>>> >>>> Cheers, >>>> Lakshmipathi.G >>>> www.giis.co.in >>>> >>>> _______________________________________________ >>>> Ext3-users mailing list >>>> Ext3-users at redhat.com >>>> https://www.redhat.com/mailman/listinfo/ext3-users >>>> >>>> >> >> >> > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users > -- Sponser and operater: Linux monitoring solution: http://admon.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From sandeen at redhat.com Mon Dec 15 16:55:20 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Mon, 15 Dec 2008 10:55:20 -0600 Subject: How to sell linux tools? In-Reply-To: <494606EB.3090208@gmail.com> References: <494601E6.7000200@gmail.com> <494606EB.3090208@gmail.com> Message-ID: <49468BF8.5020801@redhat.com> William Tambe wrote: > I don't know if this is the right discussion group for the subject, but > I am also curious to know. ?-| It's not the right list, and it should be taken elsewhere, IMHO. Thanks, -Eric From bimal_pandit at rediffmail.com Tue Dec 16 08:45:12 2008 From: bimal_pandit at rediffmail.com (bimal pandit) Date: 16 Dec 2008 08:45:12 -0000 Subject: How to sell linux tools? Message-ID: <20081216084512.14643.qmail@f5mail-236-241.rediffmail.com> Dear Lakshmi Pathi, ? On Mon, 15 Dec 2008 lakshmi pathi wrote : >Yes ....Even i like free stuffs :) ...But how could an Linux/open >source programmer earn money for living? > >Cheers, >Lakshmipathi.G > > >On Mon, Dec 15, 2008 at 12:36 PM, William Tambe wrote: > > You know we like free stuff right? > > > > lakshmi pathi wrote: > >> > >> Hi, > >> I need clarifications on how to sell linux tools. (Though i' not sure > >> how people ready to buy it :) ) > >> I have written few tools and planning to write more(by giving up > >> current non-linux & boring job). > >> I want to know,which license will allow me to sell tools/softwares? (I > >> hope to sell the products through online) > >> > >> Cheers, > >> Lakshmipathi.G > >> www.giis.co.in > >> > >> _______________________________________________ > >> Ext3-users mailing list > >> Ext3-users at redhat.com > >> https://www.redhat.com/mailman/listinfo/ext3-users > >> > > > > > >-- >Cheers, >Lakshmipathi.G > >__________________ I feel that you should adopt any two of the following models that I have seen generally people use ... while working on OSS... 1) Look for consultation services and specilised services from companies, people etc. as per the domain of your expertise. 2) Provide some extra and good features in your tool and mark them available only with the "Commercial Version" of the tool. hope this will be of some help to you. regards, Bimal Pandit -------------- next part -------------- An HTML attachment was scrubbed... URL: From raines at nmr.mgh.harvard.edu Wed Dec 17 20:35:47 2008 From: raines at nmr.mgh.harvard.edu (Paul Raines) Date: Wed, 17 Dec 2008 15:35:47 -0500 (EST) Subject: curious corruption 2-byte shift of all data Message-ID: A user of ours had a USB drive with a ext3 filesystem he was using for backup of data. He copied a ton of data to it and then was unable to mount the drive as he kept getting the message it was busy. He uses the GNOME desktop and is not a "command line" user. Having no other option he just disconnected the drive. Later he reconnected it and says he started to remove of a bunch of the files. 14 hours later he came back and the remove operation was still going on and he could not stop it. At this point he rebooted the box and then contacted me when the drive would not longer mount at all. So I look at the partition table which still seems fine: ==================================================================== # fdisk -l /dev/sdc Disk /dev/sdc: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 1 60801 488384001 83 Linux ==================================================================== But a valid filesystem cannot be found. I try to dumpe2fs it: ==================================================================== # dumpe2fs -h /dev/sdc1 dumpe2fs 1.39 (29-May-2006) dumpe2fs: Bad magic number in super-block while trying to open /dev/sdc1 Couldn't find valid filesystem superblock. [root at shadowfax ~]# dumpe2fs -h -ob32768 /dev/sdc1 dumpe2fs 1.39 (29-May-2006) dumpe2fs: Bad magic number in super-block while trying to open /dev/sdc1 Couldn't find valid filesystem superblock. ==================================================================== and so on at a bunch of backup block locations. No luck. I then do a hex dump and find something interesting: ==================================================================== 000003e0 00000000 00000000 00000000 00000000 ................ 000003f0 00000000 00000000 00000000 00000000 ................ 00000400 000000c0 a3038009 4707e026 5d000c13 ........G..&]... 00000410 bf02c980 a1030000 00000200 00000200 ................ 00000420 00000080 00000080 00000040 00001910 ........... at .... 00000430 48499d47 48492300 260053ef 02000100 HI.GHI#.&.S..... 00000440 0000ebcb 6348004e ed000000 00000100 ....cH.N........ 00000450 00000000 00000b00 00008000 00001000 ................ 00000460 00000200 00000300 0000549a de87064b ..........T....K 00000470 46e88280 10c8a6f4 74b44153 414c415a F.......t.ASALAZ 00000480 41525f55 53423100 00000000 00000000 AR_USB1......... 00000490 00000000 00000000 00000000 00000000 ................ 000004a0 00000000 00000000 00000000 00000000 ................ ==================================================================== Doing a hexdump on other ext3 filesystems and looking at the magic file, I see the bytes "53ef" are supposed to appear at 00000438. Here they appear 2 bytes further on (i.e. 0000043a). SO I try something: ==================================================================== [root at shadowfax ~]# dd if=/dev/sdc1 bs=1 count=4096 skip=2 of=/tmp/sdc1.data 4096+0 records in 4096+0 records out 4096 bytes (4.1 kB) copied, 0.01094 seconds, 374 kB/s [root at shadowfax ~]# file /tmp/sdc1.data /tmp/sdc1.data: Linux rev 1.0 ext2 filesystem data (mounted or unclean) (errors) (large files) ==================================================================== Looking at the fs label, 'ASALAZAR_USB1', it is also offset 2 bytes to the position I see in other valid ext3 filesystems I have labeled. So everythings seems shifted 2 bytes. Any idea how this happened? Any idea how to easily fix it? Any fancy Linux device tricks I can do to make /dev/sdc1 shift everything by two bytes? Right now I can only think of doing a dump shifted by 2 bytes of this disk to another disk and see if can then mount that disk. -- --------------------------------------------------------------- Paul Raines email: raines at nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street Charlestown, MA 02129 USA From jburgess777 at googlemail.com Wed Dec 17 22:13:28 2008 From: jburgess777 at googlemail.com (Jon Burgess) Date: Wed, 17 Dec 2008 22:13:28 +0000 Subject: curious corruption 2-byte shift of all data In-Reply-To: References: Message-ID: <1229552008.4760.44.camel@localhost.localdomain> On Wed, 2008-12-17 at 15:35 -0500, Paul Raines wrote: > Any > fancy Linux device tricks I can do to make /dev/sdc1 shift everything > by two bytes? losetup -o 2 e.g. [root at shark ~]# od -t x1 /dev/sda | head -n 1 0000000 eb 48 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 [root at shark ~]# losetup -o 2 /dev/loop0 /dev/sda [root at shark ~]# od -t x1 /dev/loop0 | head -n 1 0000000 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 fb be Jon From raines at nmr.mgh.harvard.edu Wed Dec 17 22:28:22 2008 From: raines at nmr.mgh.harvard.edu (Paul Raines) Date: Wed, 17 Dec 2008 17:28:22 -0500 (EST) Subject: curious corruption 2-byte shift of all data In-Reply-To: <1229552008.4760.44.camel@localhost.localdomain> References: <1229552008.4760.44.camel@localhost.localdomain> Message-ID: On Wed, 17 Dec 2008, Jon Burgess wrote: > On Wed, 2008-12-17 at 15:35 -0500, Paul Raines wrote: >> Any >> fancy Linux device tricks I can do to make /dev/sdc1 shift everything >> by two bytes? > > losetup -o 2 > > e.g. > > [root at shark ~]# od -t x1 /dev/sda | head -n 1 > 0000000 eb 48 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 > [root at shark ~]# losetup -o 2 /dev/loop0 /dev/sda > [root at shark ~]# od -t x1 /dev/loop0 | head -n 1 > 0000000 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 fb be > > Jon Perfect! THanks. Unfortunately it appears the filesystem is toast though and it was not as simple as everything being shifted by 2 bytes. So I will chalk it up as a loss. [root at shadowfax ~]# losetup -o 2 /dev/loop7 /dev/sdc1 [root at shadowfax ~]# dumpe2fs -h /dev/loop7 dumpe2fs 1.39 (29-May-2006) Filesystem volume name: ASALAZAR_USB1 Last mounted on: Filesystem UUID: 549ade87-064b-46e8-8280-10c8a6f474b4 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: resize_inode filetype sparse_super large_file Default mount options: (none) Filesystem state: not clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 61063168 Block count: 122096000 Reserved block count: 6104800 Free blocks: 46076684 Free inodes: 60915913 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 994 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16384 Inode blocks per group: 512 Filesystem created: Thu Jun 26 13:03:39 2008 Last mount time: Tue Dec 16 15:31:21 2008 Last write time: Tue Dec 16 19:28:13 2008 Mount count: 35 Maximum mount count: 38 Last checked: Thu Jun 26 13:03:39 2008 Check interval: 15552000 (6 months) Next check after: Tue Dec 23 12:03:39 2008 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Default directory hash: tea Directory Hash Seed: e41ec746-def1-4d33-9a44-8aff8caef73b ext2fs_read_bb_inode: A block group is missing an inode table [root at shadowfax ~]# e2fsck -f -n /dev/loop7 e2fsck 1.39 (29-May-2006) Group descriptors look bad... trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/loop7 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 From lists at nerdbynature.de Sun Dec 21 13:25:25 2008 From: lists at nerdbynature.de (Christian Kujau) Date: Sun, 21 Dec 2008 05:25:25 -0800 (PST) Subject: curious corruption 2-byte shift of all data In-Reply-To: References: <1229552008.4760.44.camel@localhost.localdomain> Message-ID: On Wed, 17 Dec 2008, Paul Raines wrote: > [root at shadowfax ~]# e2fsck -f -n /dev/loop7 > e2fsck 1.39 (29-May-2006) > Group descriptors look bad... trying backup blocks... > e2fsck: Bad magic number in super-block while trying to open /dev/loop7 > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 Did you try one the alternatae superblocks? (mkfs.ext3 -n might help) Last time I myself had to use this it did not work. So I'm really curious if e2fsck -b actually works when this message appears. Christian. -- BOFH excuse #78: Yes, yes, its called a design limitation From shirishag75 at gmail.com Sun Dec 21 15:31:58 2008 From: shirishag75 at gmail.com (shirish) Date: Sun, 21 Dec 2008 21:01:58 +0530 Subject: corruption happening sometimes when I do a shutdown -r now Message-ID: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> Hi all, Apologies but this is going to be a long post. I get a corruption sometime when I do a $sudo shutdown -r now This is on an ubuntu 8.10 machine. The only way to resolve the same I know is to do a sudo fsck -y /dev/sdb7 This is the output I got when I ran fsck through the Live CD $ sudo fsck -y /dev/sdb7 fsck 1.41.3 (12-Oct-2008) e2fsck 1.41.3 (12-Oct-2008) /dev/sdb7 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 991290 has illegal block(s). Clear? yes Illegal block #12 (1770618119) in inode 991290. CLEARED. Illegal block #13 (3240613319) in inode 991290. CLEARED. Illegal block #14 (2657962509) in inode 991290. CLEARED. Illegal block #15 (1989131717) in inode 991290. CLEARED. Illegal block #16 (3656511222) in inode 991290. CLEARED. Illegal block #17 (3779028861) in inode 991290. CLEARED. Illegal block #18 (2107801771) in inode 991290. CLEARED. Illegal block #19 (341962676) in inode 991290. CLEARED. Illegal block #20 (3524774831) in inode 991290. CLEARED. Illegal block #21 (2399313415) in inode 991290. CLEARED. Illegal block #22 (3961093683) in inode 991290. CLEARED. Too many illegal blocks in inode 991290. Clear inode? yes Inode 991327 has illegal block(s). Clear? yes Illegal block #12 (1936420449) in inode 991327. CLEARED. Illegal block #13 (1953849951) in inode 991327. CLEARED. Illegal block #14 (1601073012) in inode 991327. CLEARED. Illegal block #15 (858797110) in inode 991327. CLEARED. Illegal block #16 (574109749) in inode 991327. CLEARED. Illegal block #17 (1668181792) in inode 991327. CLEARED. Illegal block #18 (1801677164) in inode 991327. CLEARED. Illegal block #19 (1701978685) in inode 991327. CLEARED. Illegal block #20 (1852994932) in inode 991327. CLEARED. Illegal block #21 (1936683040) in inode 991327. CLEARED. Illegal block #22 (1752457076) in inode 991327. CLEARED. Too many illegal blocks in inode 991327. Clear inode? yes Inode 991248, i_blocks is 21744, should be 21760. Fix? yes Inode 991247, i_size is 4946696, should be 5099520. Fix? yes Inode 991247, i_blocks is 9688, should be 9984. Fix? yes Inode 991246, i_size is 3581284, should be 3719168. Fix? yes Inode 991246, i_blocks is 7008, should be 7272. Fix? yes Inode 991252 has illegal block(s). Clear? yes Illegal block #12 (73119260) in inode 991252. CLEARED. Illegal block #13 (244035658) in inode 991252. CLEARED. Illegal block #14 (4177530440) in inode 991252. CLEARED. Illegal block #15 (1086374436) in inode 991252. CLEARED. Illegal block #16 (3662801559) in inode 991252. CLEARED. Illegal block #17 (1612073856) in inode 991252. CLEARED. Illegal block #18 (1695981284) in inode 991252. CLEARED. Illegal block #19 (3159380756) in inode 991252. CLEARED. Illegal block #20 (2215936188) in inode 991252. CLEARED. Illegal block #21 (189450669) in inode 991252. CLEARED. Illegal block #22 (1425021953) in inode 991252. CLEARED. Too many illegal blocks in inode 991252. Clear inode? yes Inode 991238, i_blocks is 56, should be 128. Fix? yes Restarting e2fsck from the beginning... /dev/sdb7 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Running additional passes to resolve blocks claimed by more than one inode... Pass 1B: Rescanning for multiply-claimed blocks Multiply-claimed block(s) in inode 90119: 4685733 4685734 4685735 4685736 4685737 4685738 4685739 4685740 4685741 4685742 4685743 4685744 4685745 4685750 4685751 4685752 4685753 4127735 4127736 4127737 4127738 4688088 4688089 4688090 4688091 4688092 4688093 4688094 4688095 4688096 4688097 4688066 4688067 4688068 4688069 4688070 4688071 4688072 4688073 4688074 4688075 4688076 4688077 4688078 4688079 4688080 4688081 4688415 4689614 4689615 4689668 4689669 4689670 4689671 4690241 4127766 4688072 4688073 4688074 4688075 4688076 4688077 4688078 4688079 4688080 4688081 4688082 4688083 4688084 4688085 4685746 4685747 4685748 4685749 4685750 4685751 4685752 4685753 4685754 4685755 4685756 4685757 4685758 4685759 4685760 4685761 4685762 4685763 4685764 4685765 4685766 4685767 4685768 4685769 4685770 4685771 4685772 4685773 4685774 4685775 4685776 4685777 4688098 4688099 4688100 4688101 4688102 4688103 4688104 4688105 4688106 4688107 4688108 4688109 4688110 4688115 4688116 4688117 4688118 4688119 4688120 4688121 4688122 4688123 4688124 4688125 4688126 4688127 4688128 4688129 4688130 4688131 4688132 4688133 4688134 4688135 4688136 4688137 4688138 4688139 4688140 4688141 4688082 4688083 4688084 4688085 4688086 4688087 4688088 4688089 4688090 4688091 4688092 4688093 4688094 4688095 4688096 4688097 4688098 4688099 4688100 4688101 4688102 4688103 4688104 4688105 4688106 4688107 4688108 4688109 4688110 4688111 4688112 4688113 4688114 4688115 4688116 4688117 4688122 4688123 4688124 4688125 4688126 4688127 4688128 4688129 4688130 4688131 4688132 4688133 4688134 4688135 4688136 4688137 4688138 4688139 4688140 4688141 4688118 4688119 4688120 4688121 4685754 4685755 4685756 4685757 4685758 4685759 4685760 4685761 4685762 4685763 4685764 4685765 4685766 4685767 4685768 4685769 4685770 4685771 4685772 4685773 4685774 4685775 4685776 4685777 3981579 3981580 3981581 3981582 4688415 4689614 4689615 4689668 4689669 4689670 4689671 4690241 4127727 4127728 4127729 4127730 4127731 4127732 4127733 4127734 4127739 4127727 4127728 4127729 4127730 4127731 4127732 4127733 4127734 4127735 4127736 4127737 4127738 4127739 4127766 4688066 4688067 4688068 4688069 4688070 4688071 4688086 4688087 4685730 4685731 4685732 4685733 4685734 4685735 4685736 4685737 4685738 4685739 4685740 4685741 4685742 4685743 4685744 4685745 4685746 4685747 4685748 4685749 4688111 4688112 4688113 4688114 Multiply-claimed block(s) in inode 114733: 666688 Multiply-claimed block(s) in inode 163844: 666688 Multiply-claimed block(s) in inode 172034: 3977510 3977511 3977515 Multiply-claimed block(s) in inode 172035: 3977870 3977871 3977872 3977512 3977513 3977514 Multiply-claimed block(s) in inode 286739: 2627522 Multiply-claimed block(s) in inode 655365: 2627522 Multiply-claimed block(s) in inode 671757: 2704118 Multiply-claimed block(s) in inode 671802: 2704118 Multiply-claimed block(s) in inode 991246: 4664249 4664250 4664251 4664252 4664253 4664254 4664255 4664256 4664257 Multiply-claimed block(s) in inode 991247: 4685730 4685731 4685732 Multiply-claimed block(s) in inode 991261: 4664249 4664250 4664251 4664252 4664253 4664254 4664255 4664256 4664257 Multiply-claimed block(s) in inode 991286: 3977870 3977871 3977872 Multiply-claimed block(s) in inode 991287: 3977510 3977511 3977512 3977513 3977514 3977515 Multiply-claimed block(s) in inode 991335: 3981579 Multiply-claimed block(s) in inode 991336: 3981580 3981581 3981582 Pass 1C: Scanning directories for inodes with multiply-claimed blocks Pass 1D: Reconciling multiply-claimed blocks (There are 16 inodes containing multiply-claimed blocks.) File /shirish/StudentSexParties.Ep.1.avi (inode #90119, mod time Sun Dec 21 10:34:39 2008) has 293 multiply-claimed block(s), shared with 3 file(s): /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/_CACHE_002_ (inode #991247, mod time Sat Dec 20 06:21:29 2008) /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/4A0B1529d01 (inode #991336, mod time Thu Dec 18 11:57:04 2008) /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/2A406716d01 (inode #991335, mod time Thu Dec 18 11:56:58 2008) Clone multiply-claimed blocks? yes File /shirish/Ma.Mere.(Mi.Madre).DVDRip.[www.nosolotorrents.com]/Ma.Mere.(Mi.Madre).DVDRip.[www.nosolotorrents.com].avi (inode #114733, mod time Sat Nov 29 23:41:02 2008) has 1 multiply-claimed block(s), shared with 1 file(s): /shirish/.mozilla/firefox/h7vfyd3o.default/bookmarkbackups/bookmarks-2008-12-20.json (inode #163844, mod time Sat Dec 20 15:42:42 2008) Clone multiply-claimed blocks? yes File /shirish/.mozilla/firefox/h7vfyd3o.default/bookmarkbackups/bookmarks-2008-12-20.json (inode #163844, mod time Sat Dec 20 15:42:42 2008) has 1 multiply-claimed block(s), shared with 1 file(s): /shirish/Ma.Mere.(Mi.Madre).DVDRip.[www.nosolotorrents.com]/Ma.Mere.(Mi.Madre).DVDRip.[www.nosolotorrents.com].avi (inode #114733, mod time Sat Nov 29 23:41:02 2008) Multiply-claimed blocks already reassigned or cloned. File /shirish/Om Dar B Dar/Om Dar B Dar 1.avi (inode #172034, mod time Sun Dec 21 02:01:31 2008) has 3 multiply-claimed block(s), shared with 1 file(s): /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/07433BFDd01 (inode #991287, mod time Sat Dec 20 06:40:51 2008) Clone multiply-claimed blocks? yes File /shirish/Om Dar B Dar/Om Dar B Dar 2.avi (inode #172035, mod time Sun Dec 21 02:00:21 2008) has 6 multiply-claimed block(s), shared with 2 file(s): /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/07433BFDd01 (inode #991287, mod time Sat Dec 20 06:40:51 2008) /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/BE7CF4BDd01 (inode #991286, mod time Sat Dec 20 06:28:08 2008) Clone multiply-claimed blocks? yes File /shirish/xxx/Love_Strange_Love_vasakula1.avi (inode #286739, mod time Sat Dec 6 16:56:17 2008) has 1 multiply-claimed block(s), shared with 1 file(s): /shirish/2007-07-26-OSCON-poisonous-people.pdf (inode #655365, mod time Tue Jul 31 03:30:43 2007) Clone multiply-claimed blocks? yes File /shirish/2007-07-26-OSCON-poisonous-people.pdf (inode #655365, mod time Tue Jul 31 03:30:43 2007) has 1 multiply-claimed block(s), shared with 1 file(s): /shirish/xxx/Love_Strange_Love_vasakula1.avi (inode #286739, mod time Sat Dec 6 16:56:17 2008) Multiply-claimed blocks already reassigned or cloned. File /shirish/Music/my favs/10 Track 10.wma (inode #671757, mod time Fri Oct 17 18:48:55 2008) has 1 multiply-claimed block(s), shared with 1 file(s): /shirish/.BOINC Manager (inode #671802, mod time Sun Dec 21 10:37:27 2008) Clone multiply-claimed blocks? yes File /shirish/.BOINC Manager (inode #671802, mod time Sun Dec 21 10:37:27 2008) has 1 multiply-claimed block(s), shared with 1 file(s): /shirish/Music/my favs/10 Track 10.wma (inode #671757, mod time Fri Oct 17 18:48:55 2008) Multiply-claimed blocks already reassigned or cloned. File /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/_CACHE_001_ (inode #991246, mod time Sat Dec 20 06:22:13 2008) has 9 multiply-claimed block(s), shared with 1 file(s): /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/146A0CB9d01 (inode #991261, mod time Sat Dec 20 04:08:51 2008) Clone multiply-claimed blocks? yes File /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/_CACHE_002_ (inode #991247, mod time Sat Dec 20 06:21:29 2008) has 3 multiply-claimed block(s), shared with 1 file(s): /shirish/StudentSexParties.Ep.1.avi (inode #90119, mod time Sun Dec 21 10:34:39 2008) Multiply-claimed blocks already reassigned or cloned. File /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/146A0CB9d01 (inode #991261, mod time Sat Dec 20 04:08:51 2008) has 9 multiply-claimed block(s), shared with 1 file(s): /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/_CACHE_001_ (inode #991246, mod time Sat Dec 20 06:22:13 2008) Multiply-claimed blocks already reassigned or cloned. File /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/BE7CF4BDd01 (inode #991286, mod time Sat Dec 20 06:28:08 2008) has 3 multiply-claimed block(s), shared with 1 file(s): /shirish/Om Dar B Dar/Om Dar B Dar 2.avi (inode #172035, mod time Sun Dec 21 02:00:21 2008) Multiply-claimed blocks already reassigned or cloned. File /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/07433BFDd01 (inode #991287, mod time Sat Dec 20 06:40:51 2008) has 6 multiply-claimed block(s), shared with 2 file(s): /shirish/Om Dar B Dar/Om Dar B Dar 1.avi (inode #172034, mod time Sun Dec 21 02:01:31 2008) /shirish/Om Dar B Dar/Om Dar B Dar 2.avi (inode #172035, mod time Sun Dec 21 02:00:21 2008) Multiply-claimed blocks already reassigned or cloned. File /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/2A406716d01 (inode #991335, mod time Thu Dec 18 11:56:58 2008) has 1 multiply-claimed block(s), shared with 1 file(s): /shirish/StudentSexParties.Ep.1.avi (inode #90119, mod time Sun Dec 21 10:34:39 2008) Multiply-claimed blocks already reassigned or cloned. File /shirish/.mozilla/firefox/h7vfyd3o.default/Cache/4A0B1529d01 (inode #991336, mod time Thu Dec 18 11:57:04 2008) has 3 multiply-claimed block(s), shared with 1 file(s): /shirish/StudentSexParties.Ep.1.avi (inode #90119, mod time Sun Dec 21 10:34:39 2008) Multiply-claimed blocks already reassigned or cloned. Pass 2: Checking directory structure Entry 'F3D5384Cd01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991327. Clear? yes Entry 'BF829995d01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991353. Clear? yes Entry '27D9935Cd01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991753. Clear? yes Entry '7D64935Cd01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991755. Clear? yes Entry 'BFBD2A59d01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991290. Clear? yes Entry '5790F21Ad01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991252. Clear? yes Entry '099D7318d01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991574. Clear? yes Entry '014A935Cd01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991754. Clear? yes Entry '215F935Cd01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991756. Clear? yes Entry '50D1FFB6d01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991503. Clear? yes Entry '636F935Cd01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991757. Clear? yes Entry '22FA8E85d01' in /shirish/.mozilla/firefox/h7vfyd3o.default/Cache (991244) has deleted/unused inode 991351. Clear? yes Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: +1267420 +2263778 +3191345 +3705866 -(3971506--3971508) -(3971532--3971533) -(3971535--3971540) -3972607 -(3980408--3980414) -(3980416--3980417) -(3980423--3980443) -(3981359--3981363) -3981451 -(3981477--3981493) -(3981595--3981604) -(3981606--3981621) -(3984736--3984741) -(3994321--3994325) -3995840 +4198136 +4198436 +4210867 +4472932 Fix? yes Free blocks count wrong for group #0 (26656, counted=26485). Fix? yes Free blocks count wrong for group #38 (1, counted=0). Fix? yes Free blocks count wrong for group #65 (5, counted=2). Fix? yes Free blocks count wrong for group #69 (1, counted=0). Fix? yes Free blocks count wrong for group #97 (1, counted=0). Fix? yes Free blocks count wrong for group #113 (1, counted=0). Fix? yes Free blocks count wrong for group #121 (0, counted=103). Fix? yes Free blocks count wrong for group #125 (29, counted=0). Fix? yes Free blocks count wrong for group #128 (3, counted=0). Fix? yes Free blocks count wrong for group #136 (1, counted=0). Fix? yes Free blocks count wrong for group #143 (331, counted=0). Fix? yes Free blocks count wrong (28889238, counted=28888799). Fix? yes Inode bitmap differences: -991252 -991290 -991327 -991351 -991353 -991503 -991574 -(991753--991757) Fix? yes Free inodes count wrong for group #121 (7623, counted=7635). Fix? yes Free inodes count wrong (8474530, counted=8474542). Fix? yes /dev/sdb7: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sdb7: 4178/8478720 files (10.4% non-contiguous), 5014367/33903166 blocks Can anybody tell me what I should do so this can be prevented? Looking forward for any info. or any way the same can be averted. -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From shirishag75 at gmail.com Sun Dec 21 15:39:38 2008 From: shirishag75 at gmail.com (shirish) Date: Sun, 21 Dec 2008 21:09:38 +0530 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> Message-ID: <511f47f50812210739m7540151bi630bc7f793404db3@mail.gmail.com> Hi all, An addition, the output of dumpe2fs . The output is large hence put the same on rapidshare. http://rapidshare.com/files/175485276/dump2efs.txt.html If any info. is needed, please lemme know. -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From sandeen at redhat.com Sun Dec 21 16:03:59 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Sun, 21 Dec 2008 10:03:59 -0600 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> Message-ID: <494E68EF.20803@redhat.com> shirish wrote: > Hi all, > Apologies but this is going to be a long post. > > I get a corruption sometime when I do a $sudo shutdown -r now > > This is on an ubuntu 8.10 machine. > > The only way to resolve the same I know is to do a sudo fsck -y /dev/sdb7 > > This is the output I got when I ran fsck through the Live CD > > $ sudo fsck -y /dev/sdb7 > fsck 1.41.3 (12-Oct-2008) > e2fsck 1.41.3 (12-Oct-2008) > /dev/sdb7 contains a file system with errors, check forced. If the fs was flagged with errors, the first thing to do is to find out what that error was; it should be in the system logs. > > Can anybody tell me what I should do so this can be prevented? > > Looking forward for any info. or any way the same can be averted. Figure out what the original error was if possible, then go from there. Is this repeatable? -Eric From sandeen at redhat.com Sun Dec 21 16:49:56 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Sun, 21 Dec 2008 10:49:56 -0600 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <494E68EF.20803@redhat.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> Message-ID: <494E73B4.2040601@redhat.com> Eric Sandeen wrote: > shirish wrote: >> Hi all, >> Apologies but this is going to be a long post. >> >> I get a corruption sometime when I do a $sudo shutdown -r now >> >> This is on an ubuntu 8.10 machine. >> >> The only way to resolve the same I know is to do a sudo fsck -y /dev/sdb7 >> >> This is the output I got when I ran fsck through the Live CD >> >> $ sudo fsck -y /dev/sdb7 >> fsck 1.41.3 (12-Oct-2008) >> e2fsck 1.41.3 (12-Oct-2008) >> /dev/sdb7 contains a file system with errors, check forced. > > If the fs was flagged with errors, the first thing to do is to find out > what that error was; it should be in the system logs. Off-list shirish sent more info; the fs is being marked w/ errors via: /var/log/kern.log:Dec 19 19:55:39 shirish-desktop kernel: [ 158.989493] EXT3-fs error (device sdb7): ext3_free_blocks_sb: bit already cleared for block 493569 ... etc, which explains why it's finding an error-marked fs on fsck and why fsck finds work to do. I don't know what kernel this is running on... http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=72ed3d035855841ad611ee48b20909e9619d4a79 fixed one cause of this. Unless you can reproduce on an upstream kernel you might bug Ubuntu about it. -Eric From shirishag75 at gmail.com Sun Dec 21 16:56:04 2008 From: shirishag75 at gmail.com (shirish) Date: Sun, 21 Dec 2008 22:26:04 +0530 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <494E73B4.2040601@redhat.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> Message-ID: <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> Reply in-line :- On Sun, Dec 21, 2008 at 22:19, Eric Sandeen wrote: > Off-list shirish sent more info; the fs is being marked w/ errors via: > > /var/log/kern.log:Dec 19 19:55:39 shirish-desktop kernel: [ > 158.989493] EXT3-fs error (device sdb7): ext3_free_blocks_sb: bit > already cleared for block 493569 > > ... etc, which explains why it's finding an error-marked fs on fsck and > why fsck finds work to do. > > I don't know what kernel this is running on... Hi Eric, This is on kernel 2.6.27-11 $ uname -a Linux shirish-desktop 2.6.27-11-generic #1 SMP Fri Dec 19 16:29:52 UTC 2008 i686 GNU/Linux > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=72ed3d035855841ad611ee48b20909e9619d4a79 > > fixed one cause of this. Unless you can reproduce on an upstream kernel > you might bug Ubuntu about it. Ok cool. Would do the same. Can you tell me though what package should I be filing the bug against, the kernel or something else? > -Eric -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From sandeen at redhat.com Sun Dec 21 17:14:09 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Sun, 21 Dec 2008 11:14:09 -0600 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> Message-ID: <494E7961.5000203@redhat.com> shirish wrote: > Reply in-line :- > > On Sun, Dec 21, 2008 at 22:19, Eric Sandeen wrote: > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=72ed3d035855841ad611ee48b20909e9619d4a79 >> >> fixed one cause of this. Unless you can reproduce on an upstream kernel >> you might bug Ubuntu about it. > > Ok cool. Would do the same. Can you tell me though what package should > I be filing the bug against, the kernel or something else? > >> -Eric > yup kernel... -Eric From lists at nerdbynature.de Sun Dec 21 23:50:57 2008 From: lists at nerdbynature.de (Christian Kujau) Date: Sun, 21 Dec 2008 15:50:57 -0800 (PST) Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> Message-ID: On Sun, 21 Dec 2008, shirish wrote: > $ uname -a > Linux shirish-desktop 2.6.27-11-generic #1 SMP Fri Dec 19 16:29:52 UTC > 2008 i686 GNU/Linux > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=72ed3d035855841ad611ee48b20909e9619d4a79 >> fixed one cause of this. Unless you can reproduce on an upstream kernel >> you might bug Ubuntu about it. Hm, this commit is from 02/2007 and his Ubuntu kernel says 2.6.27 where this particular patch has been included already. Are there any other commits which may be able to fix this? > [ 158.989493] EXT3-fs error (device sdb7): ext3_free_blocks_sb: bit > already cleared for block 493569 ...could bad RAM be the reason for such a "hickup" too? Christian. -- BOFH excuse #400: We are Microsoft. What you are experiencing is not a problem; it is an undocumented feature. From sandeen at redhat.com Mon Dec 22 00:25:17 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Sun, 21 Dec 2008 18:25:17 -0600 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> Message-ID: <494EDE6D.5030901@redhat.com> Christian Kujau wrote: > On Sun, 21 Dec 2008, shirish wrote: >> $ uname -a >> Linux shirish-desktop 2.6.27-11-generic #1 SMP Fri Dec 19 16:29:52 UTC >> 2008 i686 GNU/Linux >> >>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=72ed3d035855841ad611ee48b20909e9619d4a79 >>> fixed one cause of this. Unless you can reproduce on an upstream kernel >>> you might bug Ubuntu about it. > > Hm, this commit is from 02/2007 and his Ubuntu kernel says 2.6.27 where > this particular patch has been included already. Are there any other > commits which may be able to fix this? Hmm good point, it probably is in there. >> [ 158.989493] EXT3-fs error (device sdb7): ext3_free_blocks_sb: bit >> already cleared for block 493569 > > ...could bad RAM be the reason for such a "hickup" too? It's always worth testing ram I suppose :) If Ubuntu supplies packaged unpatched upstream kernels for testing that'd be worth it too, or hand-compiling an upstream kernel perhaps. I just don't know what's in the Ubuntu kernel, and I've not seen similar reports upstream or in Fedora; the problem could be unique to his hardware, his usecase, kernel, or who knows. Reproducing a problem on a stock, known kernel will get more people interested. :) -Eric (idly wondering if we could ask Arjan to track things like ext3 shutdowns on kerneloops.org in addition to bona-fide oopses, to look for the prevalence of such things on various kernels...) From lists at nerdbynature.de Mon Dec 22 00:52:12 2008 From: lists at nerdbynature.de (Christian Kujau) Date: Sun, 21 Dec 2008 16:52:12 -0800 (PST) Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <494EDE6D.5030901@redhat.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> Message-ID: On Sun, 21 Dec 2008, Eric Sandeen wrote: > If Ubuntu supplies packaged unpatched upstream kernels for testing > that'd be worth it too, or hand-compiling an upstream kernel perhaps. I > just don't know what's in the Ubuntu kernel, and I've not seen similar FWIW, I've checked that this particular fix made it into the Ubuntu tree as well and I still think it did: http://tinyurl.com/8hn2dy > hardware, his usecase, kernel, or who knows. Reproducing a problem on a > stock, known kernel will get more people interested. :) Of course, no question about that :-) Christian. -- BOFH excuse #101: Collapsed Backbone From darkonc at gmail.com Mon Dec 22 04:18:59 2008 From: darkonc at gmail.com (Stephen Samuel) Date: Sun, 21 Dec 2008 20:18:59 -0800 Subject: curious corruption 2-byte shift of all data In-Reply-To: References: <1229552008.4760.44.camel@localhost.localdomain> Message-ID: <6cd50f9f0812212018y1f7c3b58n35935d71e929d369@mail.gmail.com> It may be that only *part* of the filesystem has been shigted by 2 bytes. Look through the partition and see if you can find blocks that look kike proper files/signatures. If that's a case later on in the filesystem, then do a binary search to see if you can figure out where the boundry is between the shifted and unshifted parts. On Wed, Dec 17, 2008 at 2:28 PM, Paul Raines wrote: > On Wed, 17 Dec 2008, Jon Burgess wrote: > > On Wed, 2008-12-17 at 15:35 -0500, Paul Raines wrote: >> >>> Any >>> fancy Linux device tricks I can do to make /dev/sdc1 shift everything >>> by two bytes? >>> >> >> losetup -o 2 >> >> e.g. >> >> [root at shark ~]# od -t x1 /dev/sda | head -n 1 >> 0000000 eb 48 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 >> [root at shark ~]# losetup -o 2 /dev/loop0 /dev/sda >> [root at shark ~]# od -t x1 /dev/loop0 | head -n 1 >> 0000000 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 fb be >> >> Jon >> > > > Perfect! THanks. > > Unfortunately it appears the filesystem is toast though and it was > not as simple as everything being shifted by 2 bytes. So I will > chalk it up as a loss. > > > > [root at shadowfax ~]# losetup -o 2 /dev/loop7 /dev/sdc1 > [root at shadowfax ~]# dumpe2fs -h /dev/loop7 > dumpe2fs 1.39 (29-May-2006) > Filesystem volume name: ASALAZAR_USB1 > Last mounted on: > Filesystem UUID: 549ade87-064b-46e8-8280-10c8a6f474b4 > Filesystem magic number: 0xEF53 > Filesystem revision #: 1 (dynamic) > Filesystem features: resize_inode filetype sparse_super large_file > Default mount options: (none) > Filesystem state: not clean with errors > Errors behavior: Continue > Filesystem OS type: Linux > Inode count: 61063168 > Block count: 122096000 > Reserved block count: 6104800 > Free blocks: 46076684 > Free inodes: 60915913 > First block: 0 > Block size: 4096 > Fragment size: 4096 > Reserved GDT blocks: 994 > Blocks per group: 32768 > Fragments per group: 32768 > Inodes per group: 16384 > Inode blocks per group: 512 > Filesystem created: Thu Jun 26 13:03:39 2008 > Last mount time: Tue Dec 16 15:31:21 2008 > Last write time: Tue Dec 16 19:28:13 2008 > Mount count: 35 > Maximum mount count: 38 > Last checked: Thu Jun 26 13:03:39 2008 > Check interval: 15552000 (6 months) > Next check after: Tue Dec 23 12:03:39 2008 > Reserved blocks uid: 0 (user root) > Reserved blocks gid: 0 (group root) > First inode: 11 > Inode size: 128 > Default directory hash: tea > Directory Hash Seed: e41ec746-def1-4d33-9a44-8aff8caef73b > ext2fs_read_bb_inode: A block group is missing an inode table > [root at shadowfax ~]# e2fsck -f -n /dev/loop7 > e2fsck 1.39 (29-May-2006) > Group descriptors look bad... trying backup blocks... > e2fsck: Bad magic number in super-block while trying to open /dev/loop7 > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 > > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users > -- Stephen Samuel http://www.bcgreen.com 778-861-7641 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shirishag75 at gmail.com Mon Dec 22 06:42:13 2008 From: shirishag75 at gmail.com (shirish) Date: Mon, 22 Dec 2008 12:12:13 +0530 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <494EDE6D.5030901@redhat.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> Message-ID: <511f47f50812212242o7444e309g517e2ee1695b62fa@mail.gmail.com> Reply in-line :- On Mon, Dec 22, 2008 at 05:55, Eric Sandeen wrote: > Christian Kujau wrote: >> Hm, this commit is from 02/2007 and his Ubuntu kernel says 2.6.27 where >> this particular patch has been included already. Are there any other >> commits which may be able to fix this? > Hmm good point, it probably is in there. Hi guys, That's what I thought. I saw the commit is from 02/2007 but don't know if this particular commit is there in kernel or not. >>> [ 158.989493] EXT3-fs error (device sdb7): ext3_free_blocks_sb: bit >>> already cleared for block 493569 >> >> ...could bad RAM be the reason for such a "hickup" too? > > It's always worth testing ram I suppose :) I can test the RAM using the memtest 86+ . Would a single series of test be good enough or should I let it run for few hours? Either way can do. Looking forward to suggestions for the same. -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From raines at nmr.mgh.harvard.edu Mon Dec 22 14:58:18 2008 From: raines at nmr.mgh.harvard.edu (Paul Raines) Date: Mon, 22 Dec 2008 09:58:18 -0500 (EST) Subject: curious corruption 2-byte shift of all data In-Reply-To: References: <1229552008.4760.44.camel@localhost.localdomain> Message-ID: Yes, I tried. No luck. On Sun, 21 Dec 2008, Christian Kujau wrote: > On Wed, 17 Dec 2008, Paul Raines wrote: >> [root at shadowfax ~]# e2fsck -f -n /dev/loop7 >> e2fsck 1.39 (29-May-2006) >> Group descriptors look bad... trying backup blocks... >> e2fsck: Bad magic number in super-block while trying to open /dev/loop7 >> >> The superblock could not be read or does not describe a correct ext2 >> filesystem. If the device is valid and it really contains an ext2 >> filesystem (and not swap or ufs or something else), then the superblock >> is corrupt, and you might try running e2fsck with an alternate superblock: >> e2fsck -b 8193 > > Did you try one the alternatae superblocks? (mkfs.ext3 -n might help) > Last time I myself had to use this it did not work. So I'm really curious > if e2fsck -b actually works when this message appears. > > Christian. > -- --------------------------------------------------------------- Paul Raines email: raines at nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street Charlestown, MA 02129 USA From raines at nmr.mgh.harvard.edu Mon Dec 22 15:01:13 2008 From: raines at nmr.mgh.harvard.edu (Paul Raines) Date: Mon, 22 Dec 2008 10:01:13 -0500 (EST) Subject: curious corruption 2-byte shift of all data In-Reply-To: <6cd50f9f0812212018y1f7c3b58n35935d71e929d369@mail.gmail.com> References: <1229552008.4760.44.camel@localhost.localdomain> <6cd50f9f0812212018y1f7c3b58n35935d71e929d369@mail.gmail.com> Message-ID: I don't have a good way to find such a boundary so we ended up just reformatting and calling it a loss. I am more interested in finding out what caused it. Obviously reconnecting a disk not properly unmounted and then writing to it again is not the right thing to do, but I would not have expected the kind of total corruption I saw. On Sun, 21 Dec 2008, Stephen Samuel wrote: > It may be that only *part* of the filesystem has been shigted by 2 bytes. > Look through the partition and see if you can find blocks that look kike > proper files/signatures. > > If that's a case later on in the filesystem, then do a binary search to see > if you can figure out where the boundry is between the shifted and unshifted > parts. > > > On Wed, Dec 17, 2008 at 2:28 PM, Paul Raines wrote: > >> On Wed, 17 Dec 2008, Jon Burgess wrote: >> >> On Wed, 2008-12-17 at 15:35 -0500, Paul Raines wrote: >>> >>>> Any >>>> fancy Linux device tricks I can do to make /dev/sdc1 shift everything >>>> by two bytes? >>>> >>> >>> losetup -o 2 >>> >>> e.g. >>> >>> [root at shark ~]# od -t x1 /dev/sda | head -n 1 >>> 0000000 eb 48 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 >>> [root at shark ~]# losetup -o 2 /dev/loop0 /dev/sda >>> [root at shark ~]# od -t x1 /dev/loop0 | head -n 1 >>> 0000000 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 fb be >>> >>> Jon >>> >> >> >> Perfect! THanks. >> >> Unfortunately it appears the filesystem is toast though and it was >> not as simple as everything being shifted by 2 bytes. So I will >> chalk it up as a loss. >> >> >> >> [root at shadowfax ~]# losetup -o 2 /dev/loop7 /dev/sdc1 >> [root at shadowfax ~]# dumpe2fs -h /dev/loop7 >> dumpe2fs 1.39 (29-May-2006) >> Filesystem volume name: ASALAZAR_USB1 >> Last mounted on: >> Filesystem UUID: 549ade87-064b-46e8-8280-10c8a6f474b4 >> Filesystem magic number: 0xEF53 >> Filesystem revision #: 1 (dynamic) >> Filesystem features: resize_inode filetype sparse_super large_file >> Default mount options: (none) >> Filesystem state: not clean with errors >> Errors behavior: Continue >> Filesystem OS type: Linux >> Inode count: 61063168 >> Block count: 122096000 >> Reserved block count: 6104800 >> Free blocks: 46076684 >> Free inodes: 60915913 >> First block: 0 >> Block size: 4096 >> Fragment size: 4096 >> Reserved GDT blocks: 994 >> Blocks per group: 32768 >> Fragments per group: 32768 >> Inodes per group: 16384 >> Inode blocks per group: 512 >> Filesystem created: Thu Jun 26 13:03:39 2008 >> Last mount time: Tue Dec 16 15:31:21 2008 >> Last write time: Tue Dec 16 19:28:13 2008 >> Mount count: 35 >> Maximum mount count: 38 >> Last checked: Thu Jun 26 13:03:39 2008 >> Check interval: 15552000 (6 months) >> Next check after: Tue Dec 23 12:03:39 2008 >> Reserved blocks uid: 0 (user root) >> Reserved blocks gid: 0 (group root) >> First inode: 11 >> Inode size: 128 >> Default directory hash: tea >> Directory Hash Seed: e41ec746-def1-4d33-9a44-8aff8caef73b >> ext2fs_read_bb_inode: A block group is missing an inode table >> [root at shadowfax ~]# e2fsck -f -n /dev/loop7 >> e2fsck 1.39 (29-May-2006) >> Group descriptors look bad... trying backup blocks... >> e2fsck: Bad magic number in super-block while trying to open /dev/loop7 >> >> The superblock could not be read or does not describe a correct ext2 >> filesystem. If the device is valid and it really contains an ext2 >> filesystem (and not swap or ufs or something else), then the superblock >> is corrupt, and you might try running e2fsck with an alternate superblock: >> e2fsck -b 8193 >> >> >> _______________________________________________ >> Ext3-users mailing list >> Ext3-users at redhat.com >> https://www.redhat.com/mailman/listinfo/ext3-users >> > > > > -- --------------------------------------------------------------- Paul Raines email: raines at nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street Charlestown, MA 02129 USA From shirishag75 at gmail.com Mon Dec 22 15:41:05 2008 From: shirishag75 at gmail.com (shirish) Date: Mon, 22 Dec 2008 21:11:05 +0530 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <494EDE6D.5030901@redhat.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> Message-ID: <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> Reply in-line :- On Mon, Dec 22, 2008 at 05:55, Eric Sandeen wrote: > Christian Kujau wrote: >>> [ 158.989493] EXT3-fs error (device sdb7): ext3_free_blocks_sb: bit >>> already cleared for block 493569 >> >> ...could bad RAM be the reason for such a "hickup" too? > > It's always worth testing ram I suppose :) Hi all, I tested RAM using memtest 86+ , ran two passes , it took about 1:30 hours doesn't show anything. If want can let it run whole night. Many a times I do get this though, maybe the hdd is failing ? [284.072041] ata2.00:exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [284.072119] ata2.00:cmd a0/00:00:00:00:00/00:00:00:00/a0 tag0 [284.072122] cdb 1b 00 00 02 00 00 00 00 00 00 00 00 [284.072124] res 40/00:03:00:00:00/00:00:00:00/a0 Emask 0x4 (timeout) [284.072300] ata2.00: status: { DRDY } This is from the Live CD, otherwise its ata1:10 most of the time when booting off the kernel as well as the status has many more things, not just DRDY . Comments, suggestions all welcome. -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From shirishag75 at gmail.com Mon Dec 22 18:03:57 2008 From: shirishag75 at gmail.com (shirish) Date: Mon, 22 Dec 2008 23:33:57 +0530 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> Message-ID: <511f47f50812221003x2a295a03x8278251485343ed@mail.gmail.com> Hi all, Finally put up this bug at launchpad and somebody was able to triage it as well. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/310279 -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From lists at nerdbynature.de Mon Dec 22 21:50:39 2008 From: lists at nerdbynature.de (Christian Kujau) Date: Mon, 22 Dec 2008 13:50:39 -0800 (PST) Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> Message-ID: On Mon, 22 Dec 2008, shirish wrote: > [284.072041] ata2.00:exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen > [284.072119] ata2.00:cmd a0/00:00:00:00:00/00:00:00:00/a0 tag0 > [284.072122] cdb 1b 00 00 02 00 00 00 00 00 00 00 00 > [284.072124] res 40/00:03:00:00:00/00:00:00:00/a0 Emask 0x4 (timeout) > [284.072300] ata2.00: status: { DRDY } So, in the end it really was hardware problems again leading to fs corruption? > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/310279 There are lots of similar bugs regarding these ata* messages, you might want to link to duplicates.... Christian. -- BOFH excuse #168: le0: no carrier: transceiver cable problem? From shirishag75 at gmail.com Tue Dec 23 04:41:20 2008 From: shirishag75 at gmail.com (shirish) Date: Tue, 23 Dec 2008 10:11:20 +0530 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> Message-ID: <511f47f50812222041vb5b64f9x5ae9a65c04d0b801@mail.gmail.com> Reply in-line :- On Tue, Dec 23, 2008 at 03:20, Christian Kujau wrote: > On Mon, 22 Dec 2008, shirish wrote: >> >> [284.072041] ata2.00:exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 >> frozen >> [284.072119] ata2.00:cmd a0/00:00:00:00:00/00:00:00:00/a0 tag0 >> [284.072122] cdb 1b 00 00 02 00 00 00 00 00 00 00 00 >> [284.072124] res 40/00:03:00:00:00/00:00:00:00/a0 Emask 0x4 >> (timeout) >> [284.072300] ata2.00: status: { DRDY } > > So, in the end it really was hardware problems again leading to fs > corruption? Hi Christian, Dunno. I also tried the smartmontools and it doesn't give any errors. I have reported my findings on the bug given below. >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/310279 > > There are lots of similar bugs regarding these ata* messages, you might want > to link to duplicates.... Which duplicates and where/what should I be searching for? > Christian. > -- > BOFH excuse #168: > > le0: no carrier: transceiver cable problem? -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From lists at nerdbynature.de Tue Dec 23 05:17:49 2008 From: lists at nerdbynature.de (Christian Kujau) Date: Mon, 22 Dec 2008 21:17:49 -0800 (PST) Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <511f47f50812222041vb5b64f9x5ae9a65c04d0b801@mail.gmail.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> <511f47f50812222041vb5b64f9x5ae9a65c04d0b801@mail.gmail.com> Message-ID: On Tue, 23 Dec 2008, shirish wrote: >>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/310279 >> >> There are lots of similar bugs regarding these ata* messages, you might want >> to link to duplicates.... > > Which duplicates and where/what should I be searching for? https://launchpad.net/+search?field.text=status%3A+DRDY ...lists quite a few of these ata messages. -- BOFH excuse #289: Interference between the keyboard and the chair. From shirishag75 at gmail.com Tue Dec 23 07:52:55 2008 From: shirishag75 at gmail.com (shirish) Date: Tue, 23 Dec 2008 13:22:55 +0530 Subject: corruption happening sometimes when I do a shutdown -r now In-Reply-To: References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> <511f47f50812222041vb5b64f9x5ae9a65c04d0b801@mail.gmail.com> Message-ID: <511f47f50812222352n4bacf042x2a333e6fb6e63718@mail.gmail.com> Reply in-line :- On Tue, Dec 23, 2008 at 10:47, Christian Kujau wrote: > https://launchpad.net/+search?field.text=status%3A+DRDY Hi Christian, Wow, that's a lot of bugs and questions. Could one of the reasons be :- a. Its an IDE hdd ? I know Ubuntu moved to SCSI emulation about a year, year and half back. One of the bugs mention a workaround involving all_generic_ide as the boot option. Would try and see if that resolves the issue. b. Could it be this output in dmesg ? $ dmesg | grep "Driver 'sd'" [ 5.704236] Driver 'sd' needs updating - please use bus_type methods What's interesting is I'm getting these issues on the newer 160 GB > ...lists quite a few of these ata messages. > -- > BOFH excuse #289: > > Interference between the keyboard and the chair. -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From lists at nerdbynature.de Tue Dec 23 08:28:04 2008 From: lists at nerdbynature.de (Christian Kujau) Date: Tue, 23 Dec 2008 00:28:04 -0800 (PST) Subject: [OT] Re: corruption happening sometimes when I do a shutdown -r now In-Reply-To: <511f47f50812222352n4bacf042x2a333e6fb6e63718@mail.gmail.com> References: <511f47f50812210731r66207f94y2806ef47e1afb36f@mail.gmail.com> <494E68EF.20803@redhat.com> <494E73B4.2040601@redhat.com> <511f47f50812210856m39296424qfc430738da51cdb2@mail.gmail.com> <494EDE6D.5030901@redhat.com> <511f47f50812220741u71541234je6b4299bcc2ddd26@mail.gmail.com> <511f47f50812222041vb5b64f9x5ae9a65c04d0b801@mail.gmail.com> <511f47f50812222352n4bacf042x2a333e6fb6e63718@mail.gmail.com> Message-ID: On Tue, 23 Dec 2008, shirish wrote: > a. Its an IDE hdd ? > I know Ubuntu moved to SCSI emulation about a year, year and half back. ITYM "moved to the new PATA/SATA IDE stack". And obviously they did in Feisty[0]. > b. Could it be this output in dmesg ? > $ dmesg | grep "Driver 'sd'" > [ 5.704236] Driver 'sd' needs updating - please use bus_type methods This one is also common[1], but really related to SCSI this time. Anyway, this has nothing to do with ext3 any more and maybe this discussion should be taken elsewhere... Christian. [0] https://blueprints.launchpad.net/ubuntu/+spec/libata-for-all-ata-disks [1] http://kerneltrap.org/mailarchive/linux-kernel/2008/1/10/555023 -- BOFH excuse #221: The mainframe needs to rest. It's getting old, you know. From davidlandy at clara.co.uk Mon Dec 29 08:43:08 2008 From: davidlandy at clara.co.uk (D Landy) Date: Mon, 29 Dec 2008 08:43:08 +0000 Subject: 32k Blocksize Support Message-ID: Hi! I'm trying to upgrade the hard drive in my PVR, without losing all my existing recordings. The trouble is, the data partition on the drive is in Ext2 format, but with 32k blocks -- so it can't be mounted in Linux, and the standard partition resizing tools won't touch it (they say it has an invalid superblock). I've managed to copy the entire old drive (80gb) to a correctly-formatted new drive (160gb) using dd, and then restored the partition table correctly (again with dd). The disk works fine, but it looks like an 80gb drive to the PVR as the superblock etc are still set for 80gb. Can anyone think of a workaround for this problem? Are there any partition resizing tools that will touch 32k-block partitions? Has anyone seen a tool that will fix up the superblock and sector allocation tables? Could anyone write one? Any help would be much appreciated. David From sandeen at redhat.com Mon Dec 29 15:18:47 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Mon, 29 Dec 2008 09:18:47 -0600 Subject: 32k Blocksize Support In-Reply-To: References: Message-ID: <4958EA57.2090908@redhat.com> D Landy wrote: > Hi! > > I'm trying to upgrade the hard drive in my PVR, without losing all my > existing recordings. > > The trouble is, the data partition on the drive is in Ext2 format, but with > 32k blocks -- so it can't be mounted in Linux, and the standard partition > resizing tools won't touch it (they say it has an invalid superblock). Where did it come from? What kind of PVR was this? Anything linux-based will be restricted to at max page-sized blocks, so if it is 32k blocks you can't mount it on an x86. > I've managed to copy the entire old drive (80gb) to a correctly-formatted > new drive (160gb) using dd, and then restored the partition table correctly > (again with dd). The disk works fine, but it looks like an 80gb drive to the > PVR as the superblock etc are still set for 80gb. > > Can anyone think of a workaround for this problem? Are there any partition > resizing tools that will touch 32k-block partitions? Has anyone seen a tool > that will fix up the superblock and sector allocation tables? Could anyone > write one? Don't confuse a partition resizer w/ a filesystem resizer, they are 2 different steps. You can use your favorite partition resizer (parted, fdisk) w/o trouble, I'd think; it won't care what the data within the partition is. So just move the end of your partition out to 160G. At that point I'd think you could do an offline resize; you can't do it online because a 4k-page linux box won't mount a 32k-block ext* filesystem, but the offline variant *should* be able to I'd think. BUT - if this is a TiVO, I'd go look for the various utilities & howtos which have been published about how to do this, and not try to roll your own procedure. -Eric > Any help would be much appreciated. > > David > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users From magawake at gmail.com Mon Dec 29 16:34:34 2008 From: magawake at gmail.com (Mag Gam) Date: Mon, 29 Dec 2008 11:34:34 -0500 Subject: inode question: ext4 and ext3 Message-ID: <1cbd6f830812290834i5dc76acdj41c096cc9a4fcaeb@mail.gmail.com> I was curious if ext4 has dynamic inode allocation. Presently, the application we run which resides on ext3; we constantly run out of inodes because each file is about 2KB but there are millions of them. Also, is ext4 going to be a module or has to be compiled into the kernel? TIA From sandeen at redhat.com Mon Dec 29 17:32:45 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Mon, 29 Dec 2008 11:32:45 -0600 Subject: inode question: ext4 and ext3 In-Reply-To: <1cbd6f830812290834i5dc76acdj41c096cc9a4fcaeb@mail.gmail.com> References: <1cbd6f830812290834i5dc76acdj41c096cc9a4fcaeb@mail.gmail.com> Message-ID: <495909BD.5030208@redhat.com> Mag Gam wrote: > I was curious if ext4 has dynamic inode allocation. Presently, the > application we run which resides on ext3; we constantly run out of > inodes because each file is about 2KB but there are millions of them. ext4 does not currently have dynamic inode allocation, though there has been some discussion of that. You can create your filesystem with more inodes from the start, though; -i bytes-per-inode (-i 2048) should be about right. > Also, is ext4 going to be a module or has to be compiled into the kernel? that depends on how you build your kernel, it's a config option. -Eric From magawake at gmail.com Mon Dec 29 17:49:38 2008 From: magawake at gmail.com (Mag Gam) Date: Mon, 29 Dec 2008 12:49:38 -0500 Subject: inode question: ext4 and ext3 In-Reply-To: <495909BD.5030208@redhat.com> References: <1cbd6f830812290834i5dc76acdj41c096cc9a4fcaeb@mail.gmail.com> <495909BD.5030208@redhat.com> Message-ID: <1cbd6f830812290949n777d4bc7p3ea0fb2798ca453a@mail.gmail.com> thanks for the response Eric. I am already setting the bytes per inode ratio :-) I suppose we can wait for brtfs On Mon, Dec 29, 2008 at 12:32 PM, Eric Sandeen wrote: > Mag Gam wrote: >> I was curious if ext4 has dynamic inode allocation. Presently, the >> application we run which resides on ext3; we constantly run out of >> inodes because each file is about 2KB but there are millions of them. > > ext4 does not currently have dynamic inode allocation, though there has > been some discussion of that. > > You can create your filesystem with more inodes from the start, though; > -i bytes-per-inode (-i 2048) should be about right. > >> Also, is ext4 going to be a module or has to be compiled into the kernel? > > that depends on how you build your kernel, it's a config option. > > -Eric > From sandeen at redhat.com Mon Dec 29 17:53:57 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Mon, 29 Dec 2008 11:53:57 -0600 Subject: inode question: ext4 and ext3 In-Reply-To: <1cbd6f830812290949n777d4bc7p3ea0fb2798ca453a@mail.gmail.com> References: <1cbd6f830812290834i5dc76acdj41c096cc9a4fcaeb@mail.gmail.com> <495909BD.5030208@redhat.com> <1cbd6f830812290949n777d4bc7p3ea0fb2798ca453a@mail.gmail.com> Message-ID: <49590EB5.8050201@redhat.com> Mag Gam wrote: > thanks for the response Eric. > > I am already setting the bytes per inode ratio :-) ... then you can set it lower, if you are still running out ... > I suppose we can wait for brtfs Well, if we are going to talk about other options, xfs is one as well, it also has dynamic inode allocation. That's better suited for another list though. :) -Eric > > > On Mon, Dec 29, 2008 at 12:32 PM, Eric Sandeen wrote: >> Mag Gam wrote: >>> I was curious if ext4 has dynamic inode allocation. Presently, the >>> application we run which resides on ext3; we constantly run out of >>> inodes because each file is about 2KB but there are millions of them. >> ext4 does not currently have dynamic inode allocation, though there has >> been some discussion of that. >> >> You can create your filesystem with more inodes from the start, though; >> -i bytes-per-inode (-i 2048) should be about right. >> >>> Also, is ext4 going to be a module or has to be compiled into the kernel? >> that depends on how you build your kernel, it's a config option. >> >> -Eric >> From magawake at gmail.com Mon Dec 29 17:55:45 2008 From: magawake at gmail.com (Mag Gam) Date: Mon, 29 Dec 2008 12:55:45 -0500 Subject: inode question: ext4 and ext3 In-Reply-To: <49590EB5.8050201@redhat.com> References: <1cbd6f830812290834i5dc76acdj41c096cc9a4fcaeb@mail.gmail.com> <495909BD.5030208@redhat.com> <1cbd6f830812290949n777d4bc7p3ea0fb2798ca453a@mail.gmail.com> <49590EB5.8050201@redhat.com> Message-ID: <1cbd6f830812290955s1788fbb0la36a956ecfaec2ed@mail.gmail.com> While still on topic, is the compression patch e2compr in the mainline kernel? On Mon, Dec 29, 2008 at 12:53 PM, Eric Sandeen wrote: > Mag Gam wrote: >> thanks for the response Eric. >> >> I am already setting the bytes per inode ratio :-) > > ... then you can set it lower, if you are still running out ... > >> I suppose we can wait for brtfs > > Well, if we are going to talk about other options, xfs is one as well, > it also has dynamic inode allocation. That's better suited for another > list though. :) > > -Eric > > >> >> >> On Mon, Dec 29, 2008 at 12:32 PM, Eric Sandeen wrote: >>> Mag Gam wrote: >>>> I was curious if ext4 has dynamic inode allocation. Presently, the >>>> application we run which resides on ext3; we constantly run out of >>>> inodes because each file is about 2KB but there are millions of them. >>> ext4 does not currently have dynamic inode allocation, though there has >>> been some discussion of that. >>> >>> You can create your filesystem with more inodes from the start, though; >>> -i bytes-per-inode (-i 2048) should be about right. >>> >>>> Also, is ext4 going to be a module or has to be compiled into the kernel? >>> that depends on how you build your kernel, it's a config option. >>> >>> -Eric >>> > > From sandeen at redhat.com Mon Dec 29 17:58:02 2008 From: sandeen at redhat.com (Eric Sandeen) Date: Mon, 29 Dec 2008 11:58:02 -0600 Subject: inode question: ext4 and ext3 In-Reply-To: <1cbd6f830812290955s1788fbb0la36a956ecfaec2ed@mail.gmail.com> References: <1cbd6f830812290834i5dc76acdj41c096cc9a4fcaeb@mail.gmail.com> <495909BD.5030208@redhat.com> <1cbd6f830812290949n777d4bc7p3ea0fb2798ca453a@mail.gmail.com> <49590EB5.8050201@redhat.com> <1cbd6f830812290955s1788fbb0la36a956ecfaec2ed@mail.gmail.com> Message-ID: <49590FAA.8060400@redhat.com> Mag Gam wrote: > While still on topic, is the compression patch e2compr in the mainline kernel? > nope -Eric > > On Mon, Dec 29, 2008 at 12:53 PM, Eric Sandeen wrote: >> Mag Gam wrote: >>> thanks for the response Eric. >>> >>> I am already setting the bytes per inode ratio :-) >> ... then you can set it lower, if you are still running out ... >> >>> I suppose we can wait for brtfs >> Well, if we are going to talk about other options, xfs is one as well, >> it also has dynamic inode allocation. That's better suited for another >> list though. :) >> >> -Eric >> >> >>> >>> On Mon, Dec 29, 2008 at 12:32 PM, Eric Sandeen wrote: >>>> Mag Gam wrote: >>>>> I was curious if ext4 has dynamic inode allocation. Presently, the >>>>> application we run which resides on ext3; we constantly run out of >>>>> inodes because each file is about 2KB but there are millions of them. >>>> ext4 does not currently have dynamic inode allocation, though there has >>>> been some discussion of that. >>>> >>>> You can create your filesystem with more inodes from the start, though; >>>> -i bytes-per-inode (-i 2048) should be about right. >>>> >>>>> Also, is ext4 going to be a module or has to be compiled into the kernel? >>>> that depends on how you build your kernel, it's a config option. >>>> >>>> -Eric >>>> >> From adam at npjh.com Sun Dec 21 00:38:02 2008 From: adam at npjh.com (Adam Flott) Date: Sun, 21 Dec 2008 00:38:02 -0000 Subject: Incorrect disk usage size Message-ID: After an aptitude safe-upgrade of Debian's testing (as of today) my root file system (ext3) seems to have "filled up" and I'm not sure how to get Linux to correctly report the used size. The drive doesn't appear to be going out as the logs haven't indicated anything suspicious yet. smartmontools didn't show anything abnormal either. $ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 48062440 46976212 0 100% / tmpfs 2031948 0 2031948 0% /lib/init/rw udev 10240 96 10144 1% /dev tmpfs 2031948 0 2031948 0% /dev/shm /dev/sda6 332671516 72230148 243542600 23% /home overflow 1024 52 972 6% /tmp $ du -sh -x / 5.6G / $ cat /proc/mounts rootfs / rootfs rw 0 0 ... /dev/sda1 / ext3 rw,errors=remount-ro,data=ordered 0 0 $ tune2fs -l /dev/sda1 tune2fs 1.41.3 (12-Oct-2008) Filesystem volume name: Last mounted on: Filesystem UUID: c565110d-be25-4655-b173-178b9c1a3032 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 3055616 Block count: 12207384 Reserved block count: 610369 Free blocks: 271557 Free inodes: 2519269 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1021 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Filesystem created: Sun Oct 26 13:12:33 2008 Last mount time: Sat Dec 20 17:04:53 2008 Last write time: Sat Dec 20 17:04:53 2008 Mount count: 1 Maximum mount count: 24 Last checked: Sat Dec 20 16:56:52 2008 Check interval: 15552000 (6 months) Next check after: Thu Jun 18 17:56:52 2009 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Journal inode: 8 Default directory hash: tea Directory Hash Seed: 57f7b146-08dd-4b8b-884e-31df7ee54afa Journal backup: inode blocks $ uname -a Linux an 2.6.26-1-amd64 #1 SMP Mon Dec 15 17:25:36 UTC 2008 x86_64 GNU/Linux I've looked for large files/directories via find (-type d/f -size +1G) and fsck'ing the partition multiple times with various options, but no luck. I tried copying a file large enough to have cp abort due to being out of disk space as well. Is there anything else I can do to besides reinstalling? Adam