Please note the new address for this forum : forum.excito.org. The old address redirects here but I don't know for how long. Thanks !
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
Can not read files from samba
Can not read files from samba
Hi.
I can view the filesystem of bubba2 in windows samba but i can not read or copy the files.
I can view the filesystem of bubba2 in windows samba but i can not read or copy the files.
Re: Can not read files from samba
Theres about a hundred reasons why that could be. Please show some respect to the people who volunteer to help you by explaining the issue in more detail.
Re: Can not read files from samba
Sorry for beeing disrespectful, I think i lost some of the text somehow in the first post.Ubi wrote:Theres about a hundred reasons why that could be. Please show some respect to the people who volunteer to help you by explaining the issue in more detail.
To fix the problem i tried, in chronological order:
-Turn of and on windows fileshare. After this i get to see the \\b2 folder with home and storage folder. But now when i try to open them i get the message that \\b2\storage is unavaliable.
-Tried a update and a restart.
-Turned the unit off, unplugged everything and waited a minute before turn on.
It is still dead, can not reach from my pc nor my pad.
Sorry if I missed something. Havent done any system changes lately.
Re: Can not read files from samba
Can you access via the ip address?
Re: Can not read files from samba
Well my unit started acting very strange toda, claiming no more space on hdd. But i have 200gb free on 2tb hdd. Got some error reportings in the web interface. Now I have done a reinstall and samba is atleast working fine 

Re: Can not read files from samba
ah a full disk would explain the behaviour. As mentioned, there are many reasons why your observed behaviour could occur. In your case your root partition was full (your 200GB free was your home partition), most likely due to oversize log files or unroutable email. Re-installing would not have been required.
Re: Can not read files from samba
Hmm how do i delete the extra stuff then? I have never used the email service, seems a bit odd to fill 9+ gb with log filesUbi wrote:ah a full disk would explain the behaviour. As mentioned, there are many reasons why your observed behaviour could occur. In your case your root partition was full (your 200GB free was your home partition), most likely due to oversize log files or unroutable email. Re-installing would not have been required.

Re: Can not read files from samba
Again, theres a lot of reasons why the drive can fill up, and you did not provide a lot of info. In the linux shell there are a few tools to investiate drive usage, such as "du" and "df".
Re: Can not read files from samba
So I got the problem agin (hdd full). I think it appears when i disconnect the hdd where i send the backupfiles, so the backupfiles end up in bubbas filesystem. I found some strange folders in root (./.cache/duplicity/ ), I deleted tham and i had free space agin. But soon after I got the problem once agin. So now I deleted the whole logfile folder. When i df I get
I have a lot of stuff in the dev folder. Are these files normal? almost every file and folder is empty.
Code: Select all
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 9621848 9608028 0 100% /
tmpfs 127868 0 127868 0% /lib/init/rw
udev 10240 136 10104 2% /dev
tmpfs 127868 4 127864 1% /dev/shm
/dev/mapper/bubba-storage
1911905828 1573661608 241124988 87% /home
overflow 1024 0 1024 0% /tmp
Code: Select all
root@b2:/dev# ls
MAKEDEV net ptyb8 ptyd8 ptyp8 ptyr8 ptyt8 ptyv8 ptyx8 ptyz8 shm ttyb6 ttyd6 ttyp6 ttyr6 ttyt6 ttyv6 ttyx6 ttyz6
block network_latency ptyb9 ptyd9 ptyp9 ptyr9 ptyt9 ptyv9 ptyx9 ptyz9 snd ttyb7 ttyd7 ttyp7 ttyr7 ttyt7 ttyv7 ttyx7 ttyz7
bubba network_throughput ptyba ptyda ptypa ptyra ptyta ptyva ptyxa ptyza stderr ttyb8 ttyd8 ttyp8 ttyr8 ttyt8 ttyv8 ttyx8 ttyz8
bus null ptybb ptydb ptypb ptyrb ptytb ptyvb ptyxb ptyzb stdin ttyb9 ttyd9 ttyp9 ttyr9 ttyt9 ttyv9 ttyx9 ttyz9
char port ptybc ptydc ptypc ptyrc ptytc ptyvc ptyxc ptyzc stdout ttyba ttyda ttypa ttyra ttyta ttyva ttyxa ttyza
console ppp ptybd ptydd ptypd ptyrd ptytd ptyvd ptyxd ptyzd tty ttybb ttydb ttypb ttyrb ttytb ttyvb ttyxb ttyzb
core ptmx ptybe ptyde ptype ptyre ptyte ptyve ptyxe ptyze ttyS0 ttybc ttydc ttypc ttyrc ttytc ttyvc ttyxc ttyzc
cpu_dma_latency pts ptybf ptydf ptypf ptyrf ptytf ptyvf ptyxf ptyzf ttyS1 ttybd ttydd ttypd ttyrd ttytd ttyvd ttyxd ttyzd
disk ptya0 ptyc0 ptye0 ptyq0 ptys0 ptyu0 ptyw0 ptyy0 ram0 ttyS2 ttybe ttyde ttype ttyre ttyte ttyve ttyxe ttyze
dm-0 ptya1 ptyc1 ptye1 ptyq1 ptys1 ptyu1 ptyw1 ptyy1 ram1 ttyS3 ttybf ttydf ttypf ttyrf ttytf ttyvf ttyxf ttyzf
fd ptya2 ptyc2 ptye2 ptyq2 ptys2 ptyu2 ptyw2 ptyy2 ram10 ttya0 ttyc0 ttye0 ttyq0 ttys0 ttyu0 ttyw0 ttyy0 urandom
full ptya3 ptyc3 ptye3 ptyq3 ptys3 ptyu3 ptyw3 ptyy3 ram11 ttya1 ttyc1 ttye1 ttyq1 ttys1 ttyu1 ttyw1 ttyy1 usbdev1.1
fuse ptya4 ptyc4 ptye4 ptyq4 ptys4 ptyu4 ptyw4 ptyy4 ram12 ttya2 ttyc2 ttye2 ttyq2 ttys2 ttyu2 ttyw2 ttyy2 usbdev1.2
i2c-0 ptya5 ptyc5 ptye5 ptyq5 ptys5 ptyu5 ptyw5 ptyy5 ram13 ttya3 ttyc3 ttye3 ttyq3 ttys3 ttyu3 ttyw3 ttyy3 vga_arbiter
i2c-1 ptya6 ptyc6 ptye6 ptyq6 ptys6 ptyu6 ptyw6 ptyy6 ram14 ttya4 ttyc4 ttye4 ttyq4 ttys4 ttyu4 ttyw4 ttyy4 watchdog
initctl ptya7 ptyc7 ptye7 ptyq7 ptys7 ptyu7 ptyw7 ptyy7 ram15 ttya5 ttyc5 ttye5 ttyq5 ttys5 ttyu5 ttyw5 ttyy5 xconsole
kmsg ptya8 ptyc8 ptye8 ptyq8 ptys8 ptyu8 ptyw8 ptyy8 ram2 ttya6 ttyc6 ttye6 ttyq6 ttys6 ttyu6 ttyw6 ttyy6 zero
log ptya9 ptyc9 ptye9 ptyq9 ptys9 ptyu9 ptyw9 ptyy9 ram3 ttya7 ttyc7 ttye7 ttyq7 ttys7 ttyu7 ttyw7 ttyy7
loop0 ptyaa ptyca ptyea ptyqa ptysa ptyua ptywa ptyya ram4 ttya8 ttyc8 ttye8 ttyq8 ttys8 ttyu8 ttyw8 ttyy8
loop1 ptyab ptycb ptyeb ptyqb ptysb ptyub ptywb ptyyb ram5 ttya9 ttyc9 ttye9 ttyq9 ttys9 ttyu9 ttyw9 ttyy9
loop2 ptyac ptycc ptyec ptyqc ptysc ptyuc ptywc ptyyc ram6 ttyaa ttyca ttyea ttyqa ttysa ttyua ttywa ttyya
loop3 ptyad ptycd ptyed ptyqd ptysd ptyud ptywd ptyyd ram7 ttyab ttycb ttyeb ttyqb ttysb ttyub ttywb ttyyb
loop4 ptyae ptyce ptyee ptyqe ptyse ptyue ptywe ptyye ram8 ttyac ttycc ttyec ttyqc ttysc ttyuc ttywc ttyyc
loop5 ptyaf ptycf ptyef ptyqf ptysf ptyuf ptywf ptyyf ram9 ttyad ttycd ttyed ttyqd ttysd ttyud ttywd ttyyd
loop6 ptyb0 ptyd0 ptyp0 ptyr0 ptyt0 ptyv0 ptyx0 ptyz0 random ttyae ttyce ttyee ttyqe ttyse ttyue ttywe ttyye
loop7 ptyb1 ptyd1 ptyp1 ptyr1 ptyt1 ptyv1 ptyx1 ptyz1 root ttyaf ttycf ttyef ttyqf ttysf ttyuf ttywf ttyyf
mapper ptyb2 ptyd2 ptyp2 ptyr2 ptyt2 ptyv2 ptyx2 ptyz2 rtc ttyb0 ttyd0 ttyp0 ttyr0 ttyt0 ttyv0 ttyx0 ttyz0
md ptyb3 ptyd3 ptyp3 ptyr3 ptyt3 ptyv3 ptyx3 ptyz3 rtc0 ttyb1 ttyd1 ttyp1 ttyr1 ttyt1 ttyv1 ttyx1 ttyz1
md0 ptyb4 ptyd4 ptyp4 ptyr4 ptyt4 ptyv4 ptyx4 ptyz4 sda ttyb2 ttyd2 ttyp2 ttyr2 ttyt2 ttyv2 ttyx2 ttyz2
mem ptyb5 ptyd5 ptyp5 ptyr5 ptyt5 ptyv5 ptyx5 ptyz5 sda1 ttyb3 ttyd3 ttyp3 ttyr3 ttyt3 ttyv3 ttyx3 ttyz3
mtd0 ptyb6 ptyd6 ptyp6 ptyr6 ptyt6 ptyv6 ptyx6 ptyz6 sda2 ttyb4 ttyd4 ttyp4 ttyr4 ttyt4 ttyv4 ttyx4 ttyz4
mtd0ro ptyb7 ptyd7 ptyp7 ptyr7 ptyt7 ptyv7 ptyx7 ptyz7 sg0 ttyb5 ttyd5 ttyp5 ttyr5 ttyt5 ttyv5 ttyx5 ttyz5
Re: Can not read files from samba
The /dev folder is a virtual file system used by Unix-like systems as an easy way to access hardware as if they were files.
They are not really files.
The same goes with /proc.
/dev/sda1 is the first partition of your HDD, and it corresponds to / (the root file system)
/dev/mapper/bubba-storage is the representation of the LVM file system that takes up the rest of the disk.
All the other stuff you see in there represents things as USB ports, network cards, etc.
In other words: ignore it.
Your df output shows that the first partition (/) is full. This is where the OS lives, and nothing much will work if it cannot write log files etc.
You need to find out what's filling it up.
This, I have never seen before:
Could you please provide the output of the following?
They are not really files.
The same goes with /proc.
/dev/sda1 is the first partition of your HDD, and it corresponds to / (the root file system)
/dev/mapper/bubba-storage is the representation of the LVM file system that takes up the rest of the disk.
All the other stuff you see in there represents things as USB ports, network cards, etc.
In other words: ignore it.
Your df output shows that the first partition (/) is full. This is where the OS lives, and nothing much will work if it cannot write log files etc.
You need to find out what's filling it up.
This, I have never seen before:
Code: Select all
overflow 1024 0 1024 0% /tmp
Code: Select all
# du -h --max-depth=1 /tmp
# cat /etc/fstab
Re: Can not read files from samba
# du -h --max-depth=1 /tmp:
cat /etc/fstab:
The external disk you see here is disconnected. I dont remember if i unmounted it in web interface or not before i moved my bubba to another place. Turned bubba off properly though.
Code: Select all
root@b2:~# du -h --max-depth=1 /tmp
0 /tmp/.ICE-unix
0 /tmp/.X11-unix
0 /tmp
Code: Select all
root@b2:~# cat /etc/fstab
/dev/mapper/bubba-storage /home ext3 defaults 0 2
/dev/sda1 / ext3 noatime,defaults 0 1
/dev/sda3 none swap sw 0 0
/proc /proc proc defaults 0 0
UUID=3028-9D4D /home/storage/extern/5000AAK_External-2 auto defaults,umask=0002,uid=1000,gid=100,iocharset=utf8 0 0
UUID=C610-0492 /home/storage/extern/5000AAK_External-1 auto defaults,umask=0002,uid=1000,gid=100,iocharset=utf8 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
Re: Can not read files from samba
It looks like a mess.
I'm not comfortable in advising you with things that could possibly cause loss of data, but here is what I would do (follow only at your own risk):
1. Boot the B2 with the rescue stick and connect to it via ssh
2. Mount /dev/sda1:
3. Edit /mnt/etc/fstab and get rid of all that crap. Here is /etc/fstab from a fresh B2 install:
4. When you have booted with the rescue stick and mounted /dev/sda1 you have the chance to examine the true directory structure of the partition, so now you can find out what is really filling it up.
Look at /tmp:
It should be empty. No files are supposed to be stored in there, it is a mountpoint only.
If /tmp is not the culprit, look at other things like /var/log. Try using du.
I'm not comfortable in advising you with things that could possibly cause loss of data, but here is what I would do (follow only at your own risk):
1. Boot the B2 with the rescue stick and connect to it via ssh
2. Mount /dev/sda1:
Code: Select all
# mount -t ext3 /dev/sda1 /mnt
Code: Select all
/dev/sda1 / ext3 noatime,defaults 0 1
/dev/mapper/bubba-storage /home ext3 defaults 0 2
/dev/sda3 none swap sw 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
/proc /proc proc defaults 0 0
Look at /tmp:
Code: Select all
# ls -la /mnt/tmp
If /tmp is not the culprit, look at other things like /var/log. Try using du.
Re: Can not read files from samba
Did a complete reinstall just as last time, but no formating or partition so i did not loose data. Figured out it was the best to the fact i deleted the log files. FTP was'nt working...
Anyway thank you for helping.
Anyway thank you for helping.
Re: Can not read files from samba
I will be away for approx a year nor. My b2 will be in a server room. If it will start acting strange again, will it be possible to rescue it with the usb stick by shell? Could also just reinstall it, would be cool, but then i have to preset the easyfind so i can find it after reinstall. Any idea?