If you don't have filesystems over 1 Terabyte, you had no problem with this.
The 32-bit inode feature introduced previously can cause a system
to panic or return an EFSCORRUPTED error when used on a filesystem
that was created prior to the introduction of that feature.
The problem occurs when starting a search for space to allocate an
inode in an allocation group > 1 Terabyte. The code does not properly
check for the last AG to scan.
Date: Sat Apr 6 11:32:00 PST 2002
Workarea:
stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs
Modid: 2.4.x-xfs:slinx:115905a
linux/fs/xfs/xfs_ialloc.c - 1.154
- merge irix6.5f:irix:115876a
fix xfs_ialloc_ag_select to not walk off the end of the perag list
when the starting inode number is beyond the maximum AG to put inodes
in.
|