search for: xfs_check

I run: xfs_check /dev/sdc10 And it reports: sb versionnum missing attr bit 10 Then I run: xfs_repair /dev/sdc10 And it reports output from 7 phases and "done". Again I run: xfs_check /dev/sdc10 And it reports: sb versionnum missing attr bit 10 Is this how it's supposed to work? Thanks for an...

...;Starting from kernel 2.6.35, you can try and then switch back. Older kernels have a bug leading to strange problems if you mount without inode64 again. For example, you can't access files & dirs that have been created with an inode >32bit anymore."" I also noted that "xfs_check" ran out of memory and so after some reading noted that it is reccommended to use "xfs_repair -n -vv" instead as it uses far less memory. One remark is so why is "xfs_check" there at all? I do have the option of moving the data elsewhere and rebuilding but this would ca...

Hi! I'm justing in the process of setting up a new fileserver for our company. I'm installing CentOS 5.3 (64 bit) on it. One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3. Now my experience with our current fileserver is that a 0.5TB ext3 filesystem needs approx half an hour to complete (and kicks in

Hi, I'm trying to set up an iscsi 12.5 TB storage for some data backup. Doing so, I had some difficulties to find the right tool, maybe it's also a question of the system settings... The server is a 32Bit CentOS 5.3 with the recent updates. Ths iscsi connection can be establised. fdisk and parted fail to create any information on the device or fail completely. using the lvm tools

Is there a way of checking an XFS filesystem for clean/dirty status while mounted? One of the checks we've long performed is an FS-level error check. This is *not a full-on fsck*, this is "asking the file system if it noted any problems". This is done while the file system is mounted and "hot". For example, here's how we'd check an ext* partition: # debugfs

hello everyone. i guess this has been asked before, but haven't found it in the faq. i have the following issue... it is not uncommon nowadays to have desktops with filesystems in the order of 500gb/1tb. now, my kubuntu (but other distros do the same) forces a fsck on ext3 every so often, no matter what. in the past it wasn't a big issue. but with sizes increasing so much, users are