Pro/Forums - View Single Post

cliff_stokes · 01-04-2009, 02:55 PM

I have a snap 1000v2. I have tried to add a 500gig Drive and get it to work. I copied the image file from the working drive and everything seem to be going well.

However I then ran a disk check on the whole thing and got an error.

================================================== ==================
01/02/2009 16:56:23 ERROR File System Check : Failed to allocate 3798204 bytes for i-node cache buffers!!!
================================================== ==================

The previous message occurred in the following context within the system log:

01/02/2009 16:56:23 INFORMATION System Initialization : Initialization Complete! Memory to be released: 20319888 bytes.
01/02/2009 16:56:23 ERROR File System Check : FSCK fatal error = 8
01/02/2009 16:56:23 ERROR File System Check : Failed to allocate 3798204 bytes for i-node cache buffers!!!
01/02/2009 16:56:22 INFORMATION File System Check : partition is clean.
01/02/2009 16:56:22 INFORMATION File System Check : Executing fsck /dev/ride0a /force /fix /fixfatal
01/02/2009 16:56:22 INFORMATION File System : Opened FDB for device 0x10006
01/02/2009 16:56:22 INFORMATION File System Check : Cleanup completed...
01/02/2009 16:56:22 INFORMATION File System Check : 698 files, 975 used, 3062 free (0 frags, 3062 blocks, 0.0%% fragmentation)
01/02/2009 16:56:22 INFORMATION File System Check : ** Phase 5 - Check cylinder groups
01/02/2009 16:56:22 INFORMATION File System Check : ** Phase 4b - Check backlinks
01/02/2009 16:56:22 INFORMATION File System Check : ** Phase 4 - Check reference counts
01/02/2009 16:56:22 INFORMATION File System Check : ** Phase 3 - Check connectivity
01/02/2009 16:56:22 INFORMATION File System Check : ** Phase 2 - Check pathnames
01/02/2009 16:56:22 INFORMATION File System Check : ** Phase 1b - Rescan for more duplicate blocks
01/02/2009 16:56:22 INFORMATION File System Check : ** Phase 1 - Check blocks and sizes
01/02/2009 16:56:21 INFORMATION File System Check : partition is clean.
01/02/2009 16:56:21 INFORMATION File System Check : Executing fsck /dev/ride0g /force /fix /fixfatal
01/02/2009 16:56:21 INFORMATION INIT: Setting IP address to 10.0.0.10
01/02/2009 16:56:14 System Initialization : Server v4.0.830

Is there something that can be done to increase the memory or turn off some service to get the memory down to be able to run the fsck.

Any help would be welcome.

Thanks

01-04-2009, 02:55 PM	#1
cliff_stokes Cooling Neophyte Join Date: Jan 2009 Location: Michigan Posts: 19	Fsck Error with Snap 1000 I have a snap 1000v2. I have tried to add a 500gig Drive and get it to work. I copied the image file from the working drive and everything seem to be going well. However I then ran a disk check on the whole thing and got an error. ================================================== ================== 01/02/2009 16:56:23 ERROR File System Check : Failed to allocate 3798204 bytes for i-node cache buffers!!! ================================================== ================== The previous message occurred in the following context within the system log: 01/02/2009 16:56:23 INFORMATION System Initialization : Initialization Complete! Memory to be released: 20319888 bytes. 01/02/2009 16:56:23 ERROR File System Check : FSCK fatal error = 8 01/02/2009 16:56:23 ERROR File System Check : Failed to allocate 3798204 bytes for i-node cache buffers!!! 01/02/2009 16:56:22 INFORMATION File System Check : partition is clean. 01/02/2009 16:56:22 INFORMATION File System Check : Executing fsck /dev/ride0a /force /fix /fixfatal 01/02/2009 16:56:22 INFORMATION File System : Opened FDB for device 0x10006 01/02/2009 16:56:22 INFORMATION File System Check : Cleanup completed... 01/02/2009 16:56:22 INFORMATION File System Check : 698 files, 975 used, 3062 free (0 frags, 3062 blocks, 0.0%% fragmentation) 01/02/2009 16:56:22 INFORMATION File System Check : Phase 5 - Check cylinder groups 01/02/2009 16:56:22 INFORMATION File System Check : Phase 4b - Check backlinks 01/02/2009 16:56:22 INFORMATION File System Check : Phase 4 - Check reference counts 01/02/2009 16:56:22 INFORMATION File System Check : Phase 3 - Check connectivity 01/02/2009 16:56:22 INFORMATION File System Check : Phase 2 - Check pathnames 01/02/2009 16:56:22 INFORMATION File System Check : Phase 1b - Rescan for more duplicate blocks 01/02/2009 16:56:22 INFORMATION File System Check : ** Phase 1 - Check blocks and sizes 01/02/2009 16:56:21 INFORMATION File System Check : partition is clean. 01/02/2009 16:56:21 INFORMATION File System Check : Executing fsck /dev/ride0g /force /fix /fixfatal 01/02/2009 16:56:21 INFORMATION INIT: Setting IP address to 10.0.0.10 01/02/2009 16:56:14 System Initialization : Server v4.0.830 Is there something that can be done to increase the memory or turn off some service to get the memory down to be able to run the fsck. Any help would be welcome. Thanks