OpenSUSE Install :: Which Filesystem To Choose For Bigger Blocksize
Apr 14, 2010
I have an application which uses 256k as blocksize. And I would like to have a filesystem which handles I/O blocksize as near as possible to this blocksize.
I can not use EXT3, because that will be to small blocks. I was getting into problem to use XFS; because that has some dependencies to the PAGESIZE in the kernel, it can not use bigger blocksizes than the PAGESIZE in the kernel.
What more opertunities do I have? Or how can I get XFS to work with bigger blocks.?
When I try to boot to OpenSUSE I get the following error during boot-up: unknown filesystem type 'reiserfs' could not mount root filesystem - exiting to /bin/sh$
This only started happening quite recently - before this I could boot to Linux quite happily.
I'm a photographer and I have a requirement find a better method of storing my photos other than multiple USB2 drives via USB hubs. Currently I use a Macbook Pro and 6 external drives connected via USB2 or FW800. 3 are a copy of the first three, kept up to day manually by running an rsync backup. I'd like to run a FreeNAS or OpenFiler NAS box using 2TB drives mirrored via software RAID. But - I would like to have the flexibility of also plugging into the drive physically for the faster throughput when necessary. My question is, is there a file system that both *nix and Mac OSX will play nice with?
I went to:Configure Desktop > Appearance > Icons > Get New Themesand I chose a new theme by clicking "Install." Now it shows it as installed (has "uninstall" button) but when I go to "Customize KDE Icons" it doesn't show up. I tried logging out and back in but it still won't show as a choice (but it's still "installed" somewhere).
I'm gonna buy a 1.5 TB HDD to put there backups, videos, and stuff like that, and i was wondering what Filesystem should i put there considering that it will be used for backups (mostly) and I must count with that drive in case of something going wrong.
With the release of openSUSE 11.3 I decided to upgrade my three-year old computer which is running 11.0 and has been running out of disk for the last few months. I bought a new 500Gb HDD and installed it as the master drive, and moved my old drive to the slave. I installed 11.3 on the new drive. Too easy.Then I tried to mount my old drive so I could move my account files across. I wasn't able to mount the drive, which uses LVM (Logical Volume Manager). Is there any reason this wouldn't be recognised by 11.3?Then I tried to mount my new drive from my old system but 11.0 doesn't have support for the ext4 filesystem. I loaded the ext4dev kernel module with no joy:
I installed OpenSUSE 11.1 on a friends computer after having a lot of trouble from ubuntu, and because I use it. It was working great when she got it home, but it locked up randomly and wouldn't unfreeze so she turned it off and when she rebooted She got an error about there not being a file system present and that she needed to run a mount command, which didn't work. After that, now it just says that there is no files system present and you ge tthe basic prompt. I had her run a live cd and run Gpartd and check and repair the partitions, but it did nothing.
I have an encrypted filesystem that I've decided I don't want encrypted anymore. Seems the easiest way to do this is simply reformat the filesystem, but I can't. If I try to do it in YaST2 I get either system error code -3005 (unknown) or -3008 (apparently in use). When I try to do it from the command line I get:
Code: frylock:/home/joel # umount /dev/sdb5 umount: /dev/sdb5: not mounted frylock:/home/joel # mkfs -t ext4 /dev/sdb5 mke2fs 1.41.9 (22-Aug-2009) /dev/sdb5 is apparently in use by the system; will not make a filesystem here! frylock:/home/joel #
It's unmounted, I don't know how to make it any less in use than that.I can't delete the partition because it's not the last logical partition in the extended partition.
I am creating a raid10 for our studio. I just realized after creating the filesystem that I would like modify one of the parameters - the blocksize. My original command:mkfs.ext4 -b 2048 -L insightRAIDvol /dev/md0I know want:mkfs.ext4 -b 4096 -L insightRAIDvol /dev/md0Is it ok to just issue this command even though a filesystem already is in place?I am hesitant to try this without knowing what the ramifications of this might be for the superblocks or some other unknown parameter to me that might cause problems in the future.As well I know I could rebuild everything from scratch but that's a day and a half of rebuilding
I have a nfs exported filesystem but after each reboot I have to restart the NFS server twice to make it actually export the filesystem.
First restart always fails with:
Code:
Shutting down kernel based NFS server: nfsd statd mountd idmapd done Starting kernel based NFS server: idmapdexportfs: Warning: /home/teradisk/Share does not support NFS export.
I have double boot (windows7 and Opensuse) on my laptop.
My problem is when try to login Opensuse says Read only file system.(While booting a lot of things FAILS(written red) because of Read only file system). So i can't login.
Cause of this problem is want to reach my Opensuse filesystem from windows7.I installed Ext2fsd software to windows7.After installed software can see my opensuse filesystem.But it looks empty from windows7.So uninstalled the software.
After that day try to login my Opensuse.While booting alot of thing fails to load it says "FAILED".and when entered my password after entering my username cant login it says ..... Read Only File System.
How can i make the filesystem Read/write permissions to my opensuse operating system.
I can't use any command beceause can't login. (I will try to boot with Opensuse Dvd)
I am running 11.2, kde4. The day before yesterday, the system updated and I think there was kernal update within that. I had no problems immediately afterward. Then I did a total shutdown for the night, and turned it back on yesterday only to find this:
Mount: wrong fs, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error In some cases useful info is found in syslog--try dmesg | tail or so Could not mount root filesystem--exiting to /bin/sh sh: cannot set terminal process group (-1): Inappropriate ioctl for device sh: no job control in this shell $
Besides the last updates from the other day, I did nothing out of the ordinary, no downloads or any system/configuration tweeks. Will I have to reinstall opensuse? or is there a way to reclaim my previous setup--or at least reclaim my files and documents? I'm running off of the 11.2 livecd.
OS openSuse 11.1 After boot its wrote: File system is clearn. bootsplash: status on console 0 changed to on. File system seems to have fatal corruptions. Running with --rebuild-tree is required - failed blogd: no message logging because /var file system is not accessible enci-hcd ohci-hcd uhci-hcd usb-jhce fsck failed for least one file system (not /). Please repair manually and reboot. The root file system is already mounted read-write. What file I have to correct?
I was extraction some file through command line then I encounter on notification from winrar. This file exist what u want to do replace never quite I don't want that winrar will prompt me to choose action. Everytime whenever this situation occur it will overwrite / skip that file Syntax I am using for unrar rar e -pmypassword filename
Upgraded from 11.1 to 11.2 using GUI (YaST and Wagon)
Machine stops on boot and says:
fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount, rw /
Attention: Only CONTROL-D will reboot the system in this maintenance mode. shutdown or reboot will not work.
While trying to boot into the normal user the system aborts the login and tells me that /home does not have write permission.
The login manager gives:
Code:
If I log in as root and do a
Code:
Or to open some files, it works and no problem seems to exist.
All this happened for the first time after running luckybackup to fusion the old files of one home directory under EXT4 with the new files from my notebook (ext3, Opensuse 11.1 KDE3) in order to come to a unified home. But then the system did not boot any more. I tried to change the owner but some files did not have write access (not even as root, "the file does not exist"). So I thought I might have a a file system problem.
So I thought: unmount the /dev/sdb1 and then do a fschk on it. Runs and was perfect. So I did run it with forcing to control inode per inode.
No error.
So I thought: you screwed up the system. I then decided to reinstall OpensSuse11.3 from the scratch and create the same user for home. I formatted the rest (/swap /boot /root) and left only /home. Installation runs brilliantly, all ok, it comes to the login..................
I have two ext3 partitions within an encrypted lvm2 volume. when i start up my system it says that there are 0.3% non contiguous blocks.
This is my steup:
When i want to repair with repair system from dvd it tells me that the repair and check operation for encrypted LVM devices is not supported. so how can i fix my filesystem?
Have been running 11.1 on a generic notebook (eRacks) just fine until a few days ago when CUPS couldn't be reached. Rather than futz more with 11.1, I decided to install 11.2 (which has been on my desktop). Using the same CD, which continues to check ok, the install has failed many times at about the same point: 87% through "copying root filesystem" in yast2. Specs: Intel P4 2.4 GHz, 1.5 GB RAM, ATI radeon PV250Lf
The HD was partitioned into /, swap, /home, and an extended partition of /opt, /var, /usr. Only / was ext4 and the rest were ext3. Tried various options: * no apic * no acpi * "noapic acpi=off" entered manually * Vesa instead of 1024x768
Each time had to edit partition table to mount the extended partitions. Always formatted /. At first didn't format the extended patitions, later formated all but /home. Then set yast2 to format / as ext3, to match the other partitions. In the sysinfo page the / partition is now shown as /mnt containing 723.6 MB out of 7 GB, still formatted as ext4. On rescan by yast2 partition manager, / shows as ext3. The install halts every time with an error while "copying root filesystem." Tried booting from the CD direct to install and to the Live OS followed by install--same result. So, hours later, went back to 11.1--which installed in minutes.
I am running Suse 11.0 and the system had stopped working. I booted from the disk and chose repair system. Now I can get to the Give root password for login and it accepts the password, but I get the line (repair filesystem) #
I can't delete any files bigger than 4 Go. I got a message telling me that my trash is full and I should empty it. But there is nothing in it. Is there any thing I can do to be able to delete files over 4 Go?
I have opensuse 11.3 installed, and my motherboard has the intel i845 chipset, one day windows had enough of the intel graphics chip and would not let me have anything but 640x480 pixels, well you cant do much with that so I put an ati card in and disabled the intenal graphics. windows was happy enough but suse could not boot - more specifically could not mount the root filesystem, saying it had errors (did a very quick fsck), could not find the journal, and I had a bad superblock. the "failsafe kernel" was no better. If I take the ati card out suse boots fine. however I do swap frequently between windows and linux and changing graphics cards between boots is somewhat irritating.
when I am pressing the shut down button inside kde I receive this nice black screen with the green status messages indicating what was done successfuly. At the unmounting file systems though I have to wait for a 20-30mins duration to finished. I have two or three network shares but even a timeout would not take more than 1 min to appear.
During the file system check of an ext3 partition at boot I get the following output:
The super-block could not be read or does not describe a correct ext2 filesystem. If the device is still 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 super-block:
I'm then forced to login in as root and given the following prompt:
I'm reluctant to do as advised by the output and run e2fsck -b because it is not an ext2 filesystem.
Although I can still enter runlevel 5, it doesn't seem to recognise mouse and keyboard input in KDE so my system is effectively redundant at the mo. For this reason any short term workarounds are welcome, but a fix is needed. This problem is part of a longer saga to do with recovering a Windows Vista installation which started failing to boot. I have used both Vista and SUSE tools to try and recover my bootloader to no avail, and this has been the result. If more detail about this is needed please ask and I can explain what I have done.
Formated new drive with ext3 on external drive on Suse 11.1 When upgraded to 11.2, drive was not connected... Could not get mounted after that... Set up another boot drive, could not get to mount. Found post with following:
Error as follows: mount: unknown filesystem type 'crypto_LUKS' Have also got to another point where superblock was incorrect. I can use terminal, but am not a linux guru... Have looked at other posts under luks, but can not find a solution.
I have a couple of 64bit Maverick installs from the minimal CD.They each have about 1100 packages installed. When I started to upgrade one to Natty with the Upgrade Manager, it told me it wanted to install 205 new packages (along with upgrading 877).205 new packages seems like a lot of growth in the minimal install.Why do I need those 205 packages?Then I looked at the minimal CD page where I saw that the minimal CD itself (which has lists of packages not the packages) grew from 15.6 to 22MB.So, did the minimal install just bloat up with Natty or what? Is there an even-more-minimal install?
I wonder if anyone can help me. A little background, I wanted to move my xp install to a bigger hard drive. I used Saikee's method and worked fine (as usual). My machine was a dual boot system, the xp partition was with little space so I get rid of my vista install, deleted its partition. That went fine also. Rebooted directly to XP.The problem is as follows:
a) In order to increase the size of my xp partition (old machine, athlon64 1gb of RAM) I moved my data partition to the left in order to have unallocated space near the xp partition. That was successful, I rebooted and everything was fine.
b) I run again Gparted and increased the size of the partition. Gparted told me the process was successfully applied. I rebooted.
c) after post I get the following error "error reading disk, press ctr-alt-del". I did it like five times and I get the same message.
d) With my xp install disk I tried fixboot and fixmbr and nothing changed
Since I have the original hd, I did it again, and the same thing happened after resizing xp partition, before the resizing process I was able to boot normally. I used Gparted live cd v 0.6.2 and as far as I recall I left "adjust to mib" option