<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: what should I do? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685251#M20864</link>
    <description>You can save the OS data using the tar or star comman. Star is preferred.&lt;BR /&gt;&lt;BR /&gt;Ensure that the array is not having problems, run array configuration utility.&lt;BR /&gt;&lt;BR /&gt;Also, I think that you only need to run fsck, if fsck cannot repair it, destroy and re-create the filesytem.&lt;BR /&gt;&lt;BR /&gt;I think that you should not destroy the array.</description>
    <pubDate>Wed, 07 Dec 2005 13:11:44 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2005-12-07T13:11:44Z</dc:date>
    <item>
      <title>what should I do?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685246#M20859</link>
      <description>[root@ecfarm2 log]# dmesg|more&lt;BR /&gt;Allocating block in system zone - block = 426328&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block &lt;BR /&gt;= 426329&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block &lt;BR /&gt;= 426330&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block &lt;BR /&gt;= 426331&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block &lt;BR /&gt;= 426332&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block &lt;BR /&gt;= 426333&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block &lt;BR /&gt;= 426334&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block &lt;BR /&gt;= 426335&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block &lt;BR /&gt;= 426336&lt;BR /&gt;EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in &lt;BR /&gt;&lt;BR /&gt;which filesystems that I recover? which mounted point?&lt;BR /&gt;&lt;BR /&gt;The linux contain 1 disk 36.4GB&lt;BR /&gt;&lt;BR /&gt;I have backed-up data.&lt;BR /&gt;what should I do to recover it&lt;BR /&gt;&lt;BR /&gt;[root@ecfarm2 log]# df -h&lt;BR /&gt;Filesystem            Size  Used Avail Use% Mounted on&lt;BR /&gt;/dev/ida/c0d0p1       2.0G  1.4G  532M  73% /&lt;BR /&gt;/dev/ida/c0d0p9        25G   21G  2.4G  90% /data5&lt;BR /&gt;/dev/ida/c0d0p8       985M  702M  234M  76% /home&lt;BR /&gt;none                  1.9G     0  1.9G   0% /dev/shm&lt;BR /&gt;/dev/ida/c0d0p7       2.9G  2.5G  295M  90% /usr&lt;BR /&gt;/dev/ida/c0d0p5       2.0G  1.9G   58M  97% /var&lt;BR /&gt;spb:/B0                27G   14G   13G  52% /nas&lt;BR /&gt;spb:/B2               266G  243G   21G  93% /mnt&lt;BR /&gt;spb:/B3                27G   24G  3.0G  89% /nas3</description>
      <pubDate>Tue, 06 Dec 2005 00:22:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685246#M20859</guid>
      <dc:creator>file system</dc:creator>
      <dc:date>2005-12-06T00:22:52Z</dc:date>
    </item>
    <item>
      <title>Re: what should I do?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685247#M20860</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Arrange for reboot and fsck of this system.&lt;BR /&gt;&lt;BR /&gt;What have you done to this system lately.&lt;BR /&gt;&lt;BR /&gt;To answer your question on restoring the data, you'll have to tell me how you backed it up in the first place.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 06 Dec 2005 03:29:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685247#M20860</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-12-06T03:29:18Z</dc:date>
    </item>
    <item>
      <title>Re: what should I do?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685248#M20861</link>
      <description>I mean backed-up is only backing up data file system except OS area.&lt;BR /&gt;&lt;BR /&gt;how can i backup  OS area?</description>
      <pubDate>Tue, 06 Dec 2005 05:17:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685248#M20861</guid>
      <dc:creator>file system</dc:creator>
      <dc:date>2005-12-06T05:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: what should I do?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685249#M20862</link>
      <description>device ida0(72,1): check if the major and minor numbers for any of your /dev/ida/* files match 72 and 1. I guess it's /dev/ida/c0d0p1 that's affected. &lt;BR /&gt;&lt;BR /&gt;touch /forcefsck&lt;BR /&gt;&lt;BR /&gt;and reboot.&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Dec 2005 17:44:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685249#M20862</guid>
      <dc:creator>Ralf Hildebrandt</dc:creator>
      <dc:date>2005-12-06T17:44:42Z</dc:date>
    </item>
    <item>
      <title>Re: what should I do?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685250#M20863</link>
      <description>back up the system, break the raid array, and test each of the drives with badblocks.  Identifiy the bad drive(s), replace, rebuild the array, and restore.</description>
      <pubDate>Wed, 07 Dec 2005 12:35:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685250#M20863</guid>
      <dc:creator>Alan_152</dc:creator>
      <dc:date>2005-12-07T12:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: what should I do?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685251#M20864</link>
      <description>You can save the OS data using the tar or star comman. Star is preferred.&lt;BR /&gt;&lt;BR /&gt;Ensure that the array is not having problems, run array configuration utility.&lt;BR /&gt;&lt;BR /&gt;Also, I think that you only need to run fsck, if fsck cannot repair it, destroy and re-create the filesytem.&lt;BR /&gt;&lt;BR /&gt;I think that you should not destroy the array.</description>
      <pubDate>Wed, 07 Dec 2005 13:11:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-should-i-do/m-p/3685251#M20864</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-12-07T13:11:44Z</dc:date>
    </item>
  </channel>
</rss>

