I was using gparted from a live usb to resize an ext4 partition and it failed while running resize2fs. The error it gave was
Code:
resize2fs: The inode is from a bad block in the inode table while trying to resize /dev/sda5
please run 'e2fsck -fy /dev/sda5' to fix the filesystem after the aborted resize operation.
[code]...
I have a machine running Arch Linux (2010, I believe) with a 6TB RAID-5 array hooked up to a Highpoint RocketRaid 2320. I've been having issues with the RAID controller's drivers and the latest Linux kernels thanks to the driver not being open-source, and as a result I am migrating the system to Windows Server.Problem is that the 6TB disk originally was comprised only of an ext4 partition.I shrunk the partition down as much as I could, and added a NTFS partition in the empty space so I could start moving files. That went fine. Problem is that now I need to shrink the ext4 partition again, move files, shrink again, etc. The second run through resize2fs is taking way longer than the first pass.It seems to be getting stuck at pass 3:
[root@nar-shaddaa rc.d]# resize2fs -p /dev/sdb3 863000000
resize2fs 1.41.14 (22-Dec-2010)
Resizing the filesystem on /dev/sdb3 to 863000000 (4k) blocks.
[code]....
I decided to take an old Gateway that I bought off a guy cheaply and turn it into a file and web server.I purchased copies of Debian 5.0.4 i386 disks (31 in all) on the advice of a friend, the disks weren't expensive, but now that Ive installed all the disks, I'm having a variety of errors
[443.110940 end request: I/O error, dev hde, sector 76021855
[443.111074] EXT3-fs error (device hde1): ext3_get_inode_loc: unable to read inode block - inode=2375715, block=9502724
INIT: cannot execute "/sbin/getty"
[Code]..
I'm currently in the process of remove a drive from an lvm. I am following this guide
[URL]
and to be honest I have also posted this question at [URL] but I have a fair amount of data at stake here and really need to make sure I'm acting safely. This is certainly not a place to button mash or guess.this is the 2nd drive that I am removing, the first one went off without a problem.However, I just received this error
Code:
resize2fs: Can't read next inode while trying to resize /dev/vg0/lvol0
and I'm not sure what it means or where to go from here. The entire output is
Code:
root@dude:/mnt# resize2fs -p /dev/vg0/lvol0 4466524456k
resize2fs 1.41.4 (27-Jan-2009)
Resizing the filesystem on /dev/vg0/lvol0 to 1116631114 (4k) blocks.
[code]....
Where is the inode table located in ext3 file system ? How can I read the entries in it ?
View 4 Replies View RelatedI'm running a small development server on Ubuntu 10.04 server 64 bit with ext4 as the File system type.
I keep on getting wrong block / inode size when I do an fsck:
Code:
I then force an fsck and the problem is solved, but given a day or two, the problem is back. This can sometime consume up to 10G of my HDD space.
Code:
Anyone, I would like to ask if it was possible to change the entries of a file's inode table ?
For example
Code...
I was wondering if I can change the entries in this inode table's entries.
For example I want to change the "Modify" entry ? I want it to reflect to day 2009-05-19 for example.
Can i do it ?
[code]...
server2 kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=44998281, block=89981174
[code]...
my server is fedora-7 and it was working fine till yesterday yester I have power failu problem after we got problem. while booting following error coming Inode 3640928 has a bad extended atribute block
View 1 Replies View RelatedI am using Wind River Linux- 2.6.27.18-WR3.0bg_standard. The problem is whenever I execute "reboot, ls, cd" and many other commands the OS prompts me an error-
"end request: i/o error, dev sda, sector "(different sector each time)" and
EXT3-fs error (device sda1):ext3_get_inode_loc:unable to read inode block- inode-4088001, block-4097027
I also executed "dmesg", it also showed similar errors. Has the disk gone bad or the kernel is corrupted?
I'm having trouble mounting hard drives and partitions - and am rather nervous about using Yast partitioner to do this. Is there something that would tell me about mount points in Yast partitioner? So far I haven't been able to find that information anywhere. I don't want to lose information on existing drives and partitions but do want to be able to access them.Some of them appear under disk information in "My Computer" but if I try to mount them I get this error message.There is no application installed that can open files of the type block device (inode/blockdevice).I was trying to edit fstab,his didn't seem straightforward either. I've been hacking this about in other Linux distros - so not entirely clueless
View 6 Replies View RelatedHow can we find the maximum size of the inode table and what decides it, and how the maximum size of volume of file system is decided ?
View 4 Replies View RelatedAbout a month and a half ago I purchased two new 500GB serial ATA hard drives from Best Buy to replace my other, very old 186GB SATA hard drive. Since then I've had issues with Linux. Sometimes when it's booting it gives a bunch of error messages, such as "failed to set xfermode," and then it boots. Other times, after INIT has started, I get ext3 errors about failing to read an inode block, then "cannot start /sbin/agetty" and "ID c5 respawning too fast," and at this point booting fails altogether. These errors seem to happen randomly. However, once the system has booted, everything seems to work fine, and there are no further issues.
I know it's not a faulty hard drive or filesystem because I've tried Linux on both hard drives numerous times, and I've reformatted many times, one time I even tried erasing one of the hard drives byte for byte and then formatting it, and still had issues.
I've tried Arch Linux, Gentoo, VectorLinux, and openSUSE, and all of them have given me these problems. The live CD's for Ubuntu 10.04, Clonezilla, and GParted all have trouble partitioning/cloning/installing to these hard drives. At this point, it's obvious to me that there is a universal problem with this particular model.
GRUB and Syslinux both work fine, and Windows XP works fine too. It's only Linux that's giving me issues.
I would rather not buy a new hard drive if I can help it, seeing as these two are almost brand new. Is there some BIOS setting that could be causing these problems? Is it some unsupported feature in the hard drives? Is it a bug in the Linux kernel?
The hard drive model is WD5000AADS. Both hard drives are this same model. My motherboard is an NForce 680i SLI.
EDIT: I've tried ext2/3, ReiserFS, and XFS, and all of them do this, so I don't think it's a filesystem issue.
I have a 14TB raid, file system is read-only and I am trying to run e2fsck -B -p -C -v -y /dev/sdb1, it goes through, but fails and says bad block/inode or fails to transfer, something like that.Is there a way I can get this to run successful, this is a production storage server, its critical.
View 13 Replies View RelatedHow does a filename is mapped to its inode ??? If I want to make our own system call and use a filename as argument how can I get its inode ,if I want to use some of member of inode structure in code. Basically I want to get the fd of the file.
View 5 Replies View RelatedIn my project, there is a requirement for adding one more attribute for file properties which keeps track of previous file copies(Copy history).
So how can we accomplish this?
can we add/store this information in inode structure?
How can i recover a file if i don't know the inode number of it? Is there a way of scanning the hard drive for inodes that has no reference?
View 1 Replies View RelatedI am running into a scenario where inode utilization (df -i)on a partition is 100% I want know
1) Is there a better way to list the total count of all files in a partition and just display total number of files in each directory in that partition I can get approx total for the entire partition by following commands
ls -Rla | wc -l
find -type f | wc -l
whereas ls -Rla gives too lengthy outptut with all the files in each directory
2) How to know inode utilization for each user or system account? There is huge number of files and how to remove it
In Linux when we resize the partition with the logical volume(LV), how is the inode adjusted?
View 1 Replies View Relatedhow can we view a file with its inode nno . eg. cat 12456 where 12345 is the inode of a file
View 3 Replies View RelatedThe filesytem is (or was ) 500Gb ext3. We had a small electrical power failure yesterday, the server do not stop but the disk array (SCSI Raid 5 disk system) restarted. This morning, the filesystem was not available (I/O error) so I reboot the front end. The fsck failed with the message: root inode is not a directory There are nearly 400Gb of data on this filesystem. Any idea to solve the problem ? Google always point to a commercial software or windows software...
View 2 Replies View RelatedI cant see the inode number of a file by running
ls -i <file>
How can i see the blocks where this inode points to? I'm talking about a yaffs2 partition.
I was rather intrigued by the large number of xfs bug fixes in the recent kernel update for Lucid.
Code:
aptitude changelog linux-image-2.6.32-23-server | grep -c xfs:
20
20!
Poking around reveals that one Dave Chinner, Principal Engineer -- SGI Australian Software Group, submitted a series of patches to deal with preventing the flushing of stale inodes. I'm trying to figure out just how relevant those patches are to the stability of XFS, especially to pre-Lucid Ubuntu systems: are they in danger of data loss? Some quick search results thrown together in an effort to asses this issue:[URL]..Quote:
Dave Chinner (9):
xfs: Don't flush stale inodes
xfs: Ensure we force all busy extents in range to disk
xfs: reclaim inodes under a write lock
xfs: Avoid inodes in reclaim when flushing from inode cache
[Code]...
I am getting this error every night at 4am (right about when the cron.daily runs). when it does this, it remounts the filesystem read only. In the AM I get yelled at by users. all it takes is an fsck to fix the problem, but it does it every night. I have tried to rebuild the journal by removing the has_journal flag, running an fsck, and then re-adding the journal... same problem.. and its always the same inode.
View 2 Replies View RelatedI was wondering if it was possible to display inodes of deleted files using a command. If yes, is it possible to recover the deleted files from their inodes?
View 1 Replies View RelatedCan we find the inode of a particular file using its inode number?
The reason is i want to know how many blocks are occupied by specific file.
if we consider block size of 1K.
if the file size is of 100 bytes. In such a case, when the file is
stored on disk, the file will occupy 100 bytes or 1K (since we have
choosen block size to be 1K) ?
I have a directory that contains some files (over a 1,000) that have a '' in the filename. There are also some good files that I need to keep. therefore I need a script to delete based on inode.
What I have thus far:
list="$(ls -il /opt/PC/log/*RPOUT*.xml)" #this gives me the list
# I need to get the inode of.
for i in $list
do
find . -inum $i -exec rm -i {} ;
echo "delete file" $i >> /home/me/tmp/del_inode.txt
done
echo 'completed'
I know this is not right ... what I know is is the 'find' is. I need to loop through the $list gleaning inodes to get all the files with '' delete. I'm not sure how. The $i gives me the whole line. I just want the first position. set $() does not seem to work ...
anyone know that the ntfs's file sytem struct? is there's a API or something other could let me get this number? Or there is actually no such number in windows like the number of inode in linux?
View 1 Replies View RelatedI was trying to move my home partition on Ubuntu, and the computer hibernated on me. I restarted it up on the live disk to survey the damage, to find that the home partition, according to fsck, "Superblock has an invalid journal (inode Clear? <y>"
It cannot be mounted, either.
I think I basically need to know whether it's possible to copy a partition whilst converting inode size, or if I need to create a new partition and copy the contents.
To give you the back story..
I have a system with 1 SSD and a raid array of 4 physical disks. One of the raid disks died, so I swapped it out, only to find the system wouldn't boot (had no bootloader?). I fired up a live session, and tried grub-install, but get an error like "The file /boot/grub/stage1 not read correctly". Looking into it, it looks like the problem discussed here which is basically something to do with the partition having an inode size of 256 instead of 128.
Taking a step back for a moment.. I can't really remember installing this system, but is it possible I partitioned the SSD to ext4, with a default inode size of 256, then when the installer tried to install grub, it basically refused to install it on the SSD, so offered to install it on one of the raid disks, which happens to be the disk that died? So until now, unbeknown to me, the bootloader has been on one of my raid disks, while the root (bootable?) partition is on the SSD. That's my best guess as to what's gone wrong anyway..
Anyhow, currently this system has the SSD with the small bootable partition with an inode size of 256. As luck would have it, the new raid disk is sitting there not doing anything yet, so I have the space needed to copy that partition or it's contents onto the new raid disk.
So the question is, can I convert the inode size whilst copying the partition? Or do I need to just clone the partition, then create a new one with the correct inode size, then copy the contents of the old partition to the new one? In the latter case, is there any hidden secret sauce that won't be copied with `cp -R` or so? I mean, if I just create a partition with the correct inode size, and flag it bootable, then `cp -R` from the old partition to this new one, will it be functionally the same? or is there something special I need to do because this is the root OS partition?