Mount Ext3 under DragonFlyBSD
Hello! I'm new (well, actually, very very very new) to DragonFlyBSD and currently doing my first steps with it. I have Ext2 and Ext3 partitions on my HDD (created under GNU/Linux) and I cannot use them under DragonFlyBSD. The problem is that when I try to mount any of them, I get the following error message: # mount /dev/ad4s3 /mnt/data/ mount: /dev/ad4s3 on /mnt/data: incorrect super block Or if I state the FS type explicitly, I get this: # mount -t ext2fs /dev/ad4s3 /mnt/data/ WARNING: R/W mount of #ad/0x40002 denied due to unsupported optional features ext2fs: /dev/ad4s3: Invalid argument The only mode I can mount these file systems in is read-only mode. However, the file systems are not usable in this mode either, because I can only list the root catalog of the corresponding FS. Any attempt to list other catalogs or read some files leads to the following error message on the screen: and a system reboot. I searched over Internet for a similar issue and found only one sane article mentioning this problem ( http://onlamp.com/pub/a/bsd/2000/11/16/Big_Scary_Daemons.html ). Its author tells that the root of the problem is the 'sparse_super' flag set on the Ext2 file system and suggest to turn this flag off: tune2fs -s off /dev/sda3 I tried it under my GNU/Linux system, but it says only: Clearing filesystem feature 'sparse_super' not supported. and does not do the job. So now I just do not know what to do. How cat I use my existing Ext2/Ext3 file systems on DragonFlyBSD? Any suggestions? Thanks. Vladimir - v...@ukr.net
Re: Install DragonFlyBSD on 32 MB RAM
Hello! On Tue, 06 Mar 2012 1:06:12 -0600 Chris Turner c.tur...@199technologies.com wrote: On 03/06/12 05:24, v...@ukr.net wrote: And also, the question about kernel build failure remains - I would appreciate any input on that case as well. Can you build GENERIC with a stock /etc/make.conf? If not, checkout a fresh source tree try a clean build. if so - you'll need to be making your kernel config file available and any build flags used if you want someone to try to fix. This particular error looks to be related to changing the VISUAL_USERCONFIG and can be found fairly simply by checking the file in question at the line where the build fails - the entire function is ifdef'ed out based on this option.. so - looks like this option is required most likely (I'm not 100%) Really - if you're making a custom kernel config and are changing options without checking what they do in the source tree - expect things to fail both in the build and while running, and expect to get your hands dirty - which means reading the source and finding out what the options do to the code. I managed to build my custom kernel by adding the string NO_WERROR=yes to the file '/etc/make.conf'. It built fine after that and now my system works with this kernel, but I am still not sure whether such trick is acceptable or not. Could somebody please shortly explain me the reasons for which warnings are treated as errors by default and give some advice on whether I should stick to such mode or not necessarily? Thanks! Vladimir - v...@ukr.net
