Mounting ext3fs partition
Hi all, I'm running FreeBSD 7.1-BETA2. I have several partitions/filesystems in my computer and I would like to have full access to all of them. I've mounted the NTFS partition without problems (though it is read-only, it's enough for me) I've compiled the kernel with the EXT2FS option. I can mount the partition with: mount -t ext2fs /dev/ad4s1 /mnt/linux note: the partition is actually a ext3fs... But if I enter the mount point and do ls, I get: ls: /mnt/linux: Bad file descriptor What am I doing wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting ext3fs partition
On Wed, 3 Dec 2008 20:45:23 +0100, Fernando Apesteguía [EMAIL PROTECTED] wrote: But if I enter the mount point and do ls, I get: ls: /mnt/linux: Bad file descriptor What am I doing wrong? Do you get the same error when the Linux partition is not mounted? I'm asking because I have a similar problem caused from a defective / missing inode. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting ext3fs partition
On Wed, Dec 3, 2008 at 2:45 PM, Fernando Apesteguía [EMAIL PROTECTED] wrote: Hi all, I'm running FreeBSD 7.1-BETA2. I have several partitions/filesystems in my computer and I would like to have full access to all of them. I've mounted the NTFS partition without problems (though it is read-only, it's enough for me) I've compiled the kernel with the EXT2FS option. I can mount the partition with: mount -t ext2fs /dev/ad4s1 /mnt/linux note: the partition is actually a ext3fs... But if I enter the mount point and do ls, I get: ls: /mnt/linux: Bad file descriptor Is is possible you are running into a case where the inode size of the partition is not the previous default for e2fsprogs of 128. I have a patch that addresses this, but I am hesitant to suggest it, since I have not yet validated that it does not trample some additional ext2 metadata. However, in the testing I've done, it has worked with all the tests I've put it through. You can verify the inode size with: tune2fs -l /dev/ad4s1 | grep Inode size It is likely 256 (the new e2fsprogs default), in which case you will not be able to see or use the mount without a fix. If you're interested in my patch, let me know and I can send it to you (the machine it is hosted on is down at the moment). Thanks, Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting ext3fs partition
On Wed, 3 Dec 2008 20:59:42 +0100, Fernando Apesteguía [EMAIL PROTECTED] wrote: Any clues? From ports: sysutils/e2fsprogs? I don't have a Linux partition here so I cannot check / confirm. Maybe you could use ext3.fsck from this port to check the file system before mounting it? -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting ext3fs partition
On Wed, Dec 3, 2008 at 9:08 PM, Josh Carroll [EMAIL PROTECTED] wrote: On Wed, Dec 3, 2008 at 2:45 PM, Fernando Apesteguía [EMAIL PROTECTED] wrote: Hi all, I'm running FreeBSD 7.1-BETA2. I have several partitions/filesystems in my computer and I would like to have full access to all of them. I've mounted the NTFS partition without problems (though it is read-only, it's enough for me) I've compiled the kernel with the EXT2FS option. I can mount the partition with: mount -t ext2fs /dev/ad4s1 /mnt/linux note: the partition is actually a ext3fs... But if I enter the mount point and do ls, I get: ls: /mnt/linux: Bad file descriptor Is is possible you are running into a case where the inode size of the partition is not the previous default for e2fsprogs of 128. I have a patch that addresses this, but I am hesitant to suggest it, since I have not yet validated that it does not trample some additional ext2 metadata. However, in the testing I've done, it has worked with all the tests I've put it through. You can verify the inode size with: tune2fs -l /dev/ad4s1 | grep Inode size It is likely 256 (the new e2fsprogs default), in which case you will not be able to see or use the mount without a fix. If you're interested in my patch, let me know and I can send it to you (the machine it is hosted on is down at the moment). Hi josh, Exactly, it is 256. So according to you, I can't use the mounted filesystem, right? Could you please explain in more detail, what the problem is? Thanks in advance. Thanks, Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting ext3fs partition
Hi josh, Exactly, it is 256. So according to you, I can't use the mounted filesystem, right? Could you please explain in more detail, what the problem is? Thanks in advance. I believe around e2fsprogs version 1.40.5 or so, they changed the default inode size from 128 to 256. The current ext2fs driver in FreeBSD has a hard-coded inode size defined: #define EXT2_INODE_SIZE128 I have a patch that dynamically determines this size, but I do not yet have a good enough understanding of the ext2/3 spec to decide if the changes I made are sufficient to fix the problem or if there is some risk of breakage because the extra 128 is required for some metadata of some sort. What happened in your case is something I was afraid of and what prompted me to look into a fix in the first place - namely, newer Linux distributions or even file systems created by e2fsprogs from ports in FreeBSD will be unusable with the current ext2fs driver, since it assumes a size of 128. There is some more information here regarding the patch and its current status: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00421.html I (or even better, someone more knowledgeable about file systems) need to read through the ext2/3 spec and determine if the changes I've made cause any breakage. Thanks, Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting ext3fs partition
On Wed, Dec 3, 2008 at 11:01 PM, Josh Carroll [EMAIL PROTECTED] wrote: Hi josh, Exactly, it is 256. So according to you, I can't use the mounted filesystem, right? Could you please explain in more detail, what the problem is? Thanks in advance. I believe around e2fsprogs version 1.40.5 or so, they changed the default inode size from 128 to 256. The current ext2fs driver in FreeBSD has a hard-coded inode size defined: #define EXT2_INODE_SIZE128 I have a patch that dynamically determines this size, but I do not yet have a good enough understanding of the ext2/3 spec to decide if the changes I made are sufficient to fix the problem or if there is some risk of breakage because the extra 128 is required for some metadata of some sort. What happened in your case is something I was afraid of and what prompted me to look into a fix in the first place - namely, newer Linux distributions or even file systems created by e2fsprogs from ports in FreeBSD will be unusable with the current ext2fs driver, since it assumes a size of 128. There is some more information here regarding the patch and its current status: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00421.html I (or even better, someone more knowledgeable about file systems) need to read through the ext2/3 spec and determine if the changes I've made cause any breakage. Ok, Thanks for the clarification and overall, thanks for the work of submitting the patch regardless of it is merged yet or not. Thanks, Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
