<?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: Device path in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268169#M11989</link>
    <description>Oh, OK,&lt;BR /&gt; &lt;BR /&gt;If you are using the LABEL thing then you don't need to know what the device name is.  You should be able to uncomment it and try "mount -a".&lt;BR /&gt; &lt;BR /&gt;Two things though. Why did it stop working? and, on a running system, you may well find that /tmp (on the root filesystem) is in use and you therefore won't be able to mount anything on to it.  You can try it but if it fails, you'll have to track down every process that has /tmp open and stop it before you will be able to mount /tmp again.  A re-boot makes this task easier.</description>
    <pubDate>Wed, 05 May 2004 09:56:24 GMT</pubDate>
    <dc:creator>Mark Grant</dc:creator>
    <dc:date>2004-05-05T09:56:24Z</dc:date>
    <item>
      <title>Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268166#M11986</link>
      <description>because the /tmp have problem when boot up , so I disable it in /etc/fstab , after bootup , the /tmp is disappeared , if I want to mount it back , what is the device path ( eg. /dev/sda2 ) of /tmp , how can I know it ? thx.</description>
      <pubDate>Wed, 05 May 2004 09:29:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268166#M11986</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-05-05T09:29:00Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268167#M11987</link>
      <description>IT depends entirely on how it was set up.  One way to guess would be to see which of your partitions seems not to be mounted with "df".    Then try and mount it.  It won't do any harm trying to mount a device if it doesn't exist.  Test it on /mnt and then, if you find the right one, then put the entry back in fstab and re-boot.&lt;BR /&gt; &lt;BR /&gt;You might be able to look through previous boot logs to see which devices have been mounted in the past.  You can also use "fdisk" on your drives to see which partitions have linux filesystems on and compare this with what you already have mouned.&lt;BR /&gt; &lt;BR /&gt;Don't expect to easily be able to mount it back on /tmp easily without a re-boot.</description>
      <pubDate>Wed, 05 May 2004 09:35:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268167#M11987</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2004-05-05T09:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268168#M11988</link>
      <description>thx Mark,&lt;BR /&gt;&lt;BR /&gt;this is my /etc/fstab&lt;BR /&gt;&lt;BR /&gt;LABEL=/                 /                    ext3    defaults           1 1&lt;BR /&gt;LABEL=/boot             /boot                ext3    defaults           1 2&lt;BR /&gt;none                    /dev/pts             devpts  gid=5,mode=620     0 0&lt;BR /&gt;LABEL=/home             /home                ext3    defaults,usrquota  1 2&lt;BR /&gt;none                    /proc                proc    defaults           0 0&lt;BR /&gt;none                    /dev/shm             tmpfs   defaults           0 0&lt;BR /&gt;#LABEL=/tmp              /tmp                 ext3    defaults           1 2&lt;BR /&gt;LABEL=/usr              /usr                 ext3    defaults           1 2&lt;BR /&gt;LABEL=/var              /var                 ext3    defaults           1 2&lt;BR /&gt;/dev/sda5               swap                 swap    defaults           0 0&lt;BR /&gt;/dev/cdrom              /mnt/cdrom           iso9660 noauto,owner,kudzu,ro 0 0&lt;BR /&gt;/dev/fd0                /mnt/floppy          auto    noauto,owner,kudzu 0 0&lt;BR /&gt;~&lt;BR /&gt;&lt;BR /&gt;because the /tmp can't be mount when boot , so i disable it ( as above ) , &lt;BR /&gt;I tried to find it on the boot.log , but can't find it , &lt;BR /&gt;besides the /users path also disappear after I have modified the /etc/fstab , is it possible mount it back without reboot ? thx.</description>
      <pubDate>Wed, 05 May 2004 09:47:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268168#M11988</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-05-05T09:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268169#M11989</link>
      <description>Oh, OK,&lt;BR /&gt; &lt;BR /&gt;If you are using the LABEL thing then you don't need to know what the device name is.  You should be able to uncomment it and try "mount -a".&lt;BR /&gt; &lt;BR /&gt;Two things though. Why did it stop working? and, on a running system, you may well find that /tmp (on the root filesystem) is in use and you therefore won't be able to mount anything on to it.  You can try it but if it fails, you'll have to track down every process that has /tmp open and stop it before you will be able to mount /tmp again.  A re-boot makes this task easier.</description>
      <pubDate>Wed, 05 May 2004 09:56:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268169#M11989</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2004-05-05T09:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268170#M11990</link>
      <description>Compare the output of 'mount' with your running system, and the output of 'fdisk -l /dev/sda'.&lt;BR /&gt;&lt;BR /&gt;All the filesystems created as 'Linux' should have a mount point somewhere.</description>
      <pubDate>Wed, 05 May 2004 18:00:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268170#M11990</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-05-05T18:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268171#M11991</link>
      <description>thx reply ,&lt;BR /&gt;&lt;BR /&gt;may be my /tmp have problem , I tried to run fsck but fail , could suggest what can I do ?&lt;BR /&gt;&lt;BR /&gt;# /sbin/fsck /tmp&lt;BR /&gt;fsck 1.27 (8-Mar-2002)&lt;BR /&gt;e2fsck 1.27 (8-Mar-2002)&lt;BR /&gt;fsck.ext2: Is a directory while trying to open /tmp&lt;BR /&gt;&lt;BR /&gt;The superblock could not be read or does not describe a correct ext2&lt;BR /&gt;filesystem.  If the device is valid and it really contains an ext2&lt;BR /&gt;filesystem (and not swap or ufs or something else), then the superblock&lt;BR /&gt;is corrupt, and you might try running e2fsck with an alternate superblock:&lt;BR /&gt;    e2fsck -b 8193 &lt;DEVICE&gt;&lt;/DEVICE&gt;</description>
      <pubDate>Wed, 05 May 2004 21:27:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268171#M11991</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-05-05T21:27:56Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268172#M11992</link>
      <description>Show us the output of the following two commands:&lt;BR /&gt;&lt;BR /&gt;cat /etc/fstab&lt;BR /&gt;mount&lt;BR /&gt;&lt;BR /&gt;We'll say where to go next.</description>
      <pubDate>Wed, 05 May 2004 22:27:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268172#M11992</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-05-05T22:27:58Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268173#M11993</link>
      <description>Hi,&lt;BR /&gt; Currently your /tmp is not a FS it is a directory in the /  FS (root FS). Because at the booting time the entry for /tmp was commented in /etc/fstab. So fsck will definitely fail. &lt;BR /&gt; You need to find the unmounted /tmp FS device file by comparing the fdisk, df and &lt;BR /&gt;mount outputs.</description>
      <pubDate>Thu, 06 May 2004 03:55:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268173#M11993</guid>
      <dc:creator>V.Tamilvanan</dc:creator>
      <dc:date>2004-05-06T03:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268174#M11994</link>
      <description>Hi,&lt;BR /&gt;First of all remove the # from the /tmp filesystem in fstab.&lt;BR /&gt;Go to single user mode via init 1 &lt;BR /&gt;try to come in multiuser mode vi init 2 and then init 3 and see all the filesystems are getting mounted or not&lt;BR /&gt;if you are stuck at bcheckrc for /tmp then&lt;BR /&gt;use:&lt;BR /&gt;e2fsck -b 8193 /tmp&lt;BR /&gt;&lt;BR /&gt;Regs</description>
      <pubDate>Thu, 06 May 2004 05:49:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268174#M11994</guid>
      <dc:creator>Shaikh Imran</dc:creator>
      <dc:date>2004-05-06T05:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: Device path</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268175#M11995</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You should find the device name of /tmp by using follow command.&lt;BR /&gt;&lt;BR /&gt;- find linux file system device&lt;BR /&gt;&lt;BR /&gt;   fdisk -l /dev/hda  ( if you use SCSI disk, /dev/sda, etc. )&lt;BR /&gt;&lt;BR /&gt;- find label=/tmp device&lt;BR /&gt;&lt;BR /&gt;   e2label /dev/hda1&lt;BR /&gt;   e2label /dev/hda2 ...(result of fdisk ...)&lt;BR /&gt;   :::&lt;BR /&gt;&lt;BR /&gt;- fsck&lt;BR /&gt;&lt;BR /&gt;   e2fsck -y /dev/hda2 ( device name that you find bellow steps )&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;or recreate /tmp by mke2fs command.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;</description>
      <pubDate>Fri, 07 May 2004 04:18:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path/m-p/3268175#M11995</guid>
      <dc:creator>Kiyoshi Miyake</dc:creator>
      <dc:date>2004-05-07T04:18:02Z</dc:date>
    </item>
  </channel>
</rss>

